skill-tokens
Skill0 starsChanged 29 days agoMITView on GitHub
Measures what skills and plugins cost in context on every message, against each tool's budget. Use when skills stopped firing after installing more, or to slim a plugin.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skill-benchSkill
- skill-checkSkill
- skill-competeSkill
- skill-createSkill
- skill-descriptionSkill
- skill-evalSkill
- skill-factsSkill
- skill-improveSkill
- skill-learnSkill
- skill-packageSkill
- skill-planSkill
- skill-pluginSkill
- skill-publishSkill
- skill-releaseSkill
- skill-repoSkill
- skillSkill
- skill-tidySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
After each change, run tokens again and show the before and after.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What skills cost
Every installed skill's name and description sit in context on every message, whether it's used or not. Tools cap that list: Claude Code at 1% of the model's context window and Codex at 2% (their documentation, October 2026). When the list overflows, descriptions are dropped and those skills can't be matched to a request any more, so they go quiet. This measures how close a person is to that.
npx -y @thenavidm/skill-builder@latest tokens <skill-or-plugin>(skill-builder tokens <skill-or-plugin> where it's installed globally.)
Reading the result
- every message: the skill's name and description. This is the cost that adds up across everything they have installed.
- when it runs: its
SKILL.mdbody, paid only when it fires. - files it can load: references it reads only when a step needs them.
- The plugin's share of each tool's budget on a 200,000-token model and on a 1,000,000-token one. Over 100% means this plugin alone overflows the list on that model.
The numbers are estimates at about 3 characters a token, measured against Claude Code's own counts (19 October 2026). Say so when you quote them.
When it's too heavy
In order of how much each saves:
- Shorten descriptions. What it does and when, in about 300 characters. Lists of keywords cost the most and help the least.
- Fewer skills that start on their own. A plugin's entry skill can route to the rest; skills that only run when asked (
disable-model-invocation: true) can leave the list in Claude Code and Cursor. - Merge skills that always run together.
- Move detail out of
SKILL.mdinto references, to cut the cost when it runs.
After each change, run tokens again and show the before and after. If they also have evals/triggers.json, run skill-builder trigger to confirm the shorter descriptions still fire.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

