vault-token-optimizer
Skill32 starsChanged 18 days agoMITView on GitHub
Optimize any Markdown or Obsidian vault for Claude Code by analyzing structure first, generating manifests, routing work to CLI/MCP/cache/delta, and minimizing token use. Use when working on vault audits, vault migrations, Obsidian cleanup, TricorderKit, a linked private project, or large Markdown repositories.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Albertmestre1256/obsidian-genesistheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Albertmestre1256/obsidian-genesis★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- open-source-jp-scraperSkill
- agent-config-auditSkill
- claude-code-routerSkill
- code-correctorSkill
- consolidate-memorySkill
- dev-protocolSkill
- docmancerSkill
- doc-to-skillSkill
- god-modeSkill
- rtkSkill
- session-memorySkill
- skill-creatorSkill
- skill-managerSkill
- subtitle-fixSkill
- tk-bootSkill
- tk-grillSkill
- tk-orchestratorSkill
- token-saviorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not read the whole vault.
- Distinctive: line 14
If missing, run the analyzer and manifest scripts.
- Distinctive: line 18
Create a dry-run before modifying.
≈ “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
Vault Token Optimizer
Core rule
Do not read the whole vault. Generate or read the manifest first.
Protocol
- Check
.tricorderkit/index/manifest.jsonl. - If missing, run the analyzer and manifest scripts.
- Read
initial_analysis.md. - Generate or read
router.generated.json. - Decide route: direct read, Grep, CLI, cache/delta, or MCP.
- Create a dry-run before modifying.
- Audit after modification.
Supporting files
- TOKEN_BUDGET.md
- ROUTER_CLI_MCP.md
- VAULT_ADAPTATION_PROTOCOL.md
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.