repos
Skill3.3k starsChanged 3 days agoApache-2.0View on GitHub
List every repository TokenEconomizer keeps state for (how each was identified, its agents and sessions, the checkouts seen), or merge one repository's state into another. Use when the user asks which repositories TokenEconomizer tracks, why state looks split or missing, or asks to merge or migrate it.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
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
- could be automatic: a setting could enforce it
- Distinctive: line 9
Run this command in the repository's root directory:
- Very specific: line 15
Use list as ARGS unless the user asked to migrate, or to merge KEY [INTO] (keys as the list shows them.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TokenEconomizer: repos
Run this command in the repository's root directory:
"${TOKENECONOMIZER_HOME:-$HOME/.tokeneconomizer}/bin/te" --host codex --cwd "$(pwd)" repos ARGSUse list as ARGS unless the user asked to migrate, or to merge KEY [INTO] (keys as the list shows them; INTO defaults to this repository). Never run migrate or merge unless the user asked for it. Show the output verbatim in a code block.
migrate and merge move state between repositories; that writes TokenEconomizer's own state under ~/.tokeneconomizer, outside the workspace, which the sandbox keeps read-only: run that command with sandbox_permissions set to "require_escalated" and a one-line justification, so that Codex asks the user to approve it. list reads only and needs no approval.
The command reads and writes only TokenEconomizer's own state (under ~/.tokeneconomizer);
it makes no model call, and a merge keeps the old state directory under
~/.tokeneconomizer/merged/. If it reports that the launcher does not exist, the plugin has
not run in a session yet: ask the user to start a new Codex session in this repository first.
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ecosyste-ms/claude-plugin★ 3same name
- ecosyste-ms/skills★ 2same name
- lukasrepublic/agentic-foundry★ 1same name
- jorekai/skills★ 0same 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- configSkill
- microskillsSkill
- statusSkill
- toolpruneSkill
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.