domains / families / security / tokenleak

tokenleak

authentic

Token-lean rules for coding agents: cut the context re-sent on every later call (big reads, noisy logs, re-reads, serial calls) without losing correctness.

When to use

• Use on coding tasks that read files, run tests, builds or installs, use git, or search a codebase.
• Use when the user wants to save tokens, reduce cost, or stay under usage limits.
• Use when a session keeps hitting compaction because tool output fills the context.

When not to use

• The savings depend on the workload and the model: in the benchmark a short test-fixing task gained 5%, noisy builds and multi-file features 24-51%; small models such as Haiku 4.5 barely follow the rules without the plugin's read guard.
• The benchmark covers two models and four small tasks on a synthetic repo, and runs vary 2 to 4x.
• The rules cost about 850 tokens of context themselves; on very short sessions they may not pay for themselves.
• The companion transcript audit (`tokenleak.py`) lives in the source repo and is not included here.

Skill page

Source