agentleFS
th3r-devth3r-dev/th3-skills/skills/agent-kit/SKILL.md

agent-kit

Skill2 starsChanged 2 days agoMITView on GitHub

Agent toolkit, one skill with sub-skills for running Claude Code agents cheaply. (1) cost: route each agent to the cheapest model tier that can finish it, give it a checkable finish line, skip agents the task doesn't need, with a PreToolUse hook that nudges Agent calls that set no model; (2) prompt-cache: keep agent prompt prefixes byte-identical so the prompt cache hits, with a uv-run script that builds a fingerprinted project outline, writes agent briefs and reports per-agent hit rate. Use WHENEVER you are about to spawn subagents, forks, parallel agents or a Workflow, run /loop or ScheduleWakeup, pick a model for an agent, or the user says "save tokens", "agent cost", "which model", "prompt caching", "cache hit", "token usage", "ลด token". Read the sub-skill's SKILL.md before acting.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

agent-kit: sub-skills

When the work is…ReadScripts
spawning agents, "which model for this agent", "too many agents", "agent cost"cost/SKILL.mdcost/scripts/agent_guard.py (PreToolUse hook, --selftest)
fanning out agents that share context, /loop, "cache hit rate", "prompt caching"prompt-cache/SKILL.mdprompt-cache/scripts/pcache.py (build · brief · stats · --self-test)

They chain: cost decides whether to spawn and on which tier; prompt-cache makes the briefs those agents get share one cached prefix, then measures it.

Rules every sub-skill keeps

  • No agent is free. Count the brief, the re-read and the summary against doing it inline.
  • Measure, don't estimate. Report hit rates and token counts from the session logs (pcache.py stats).
  • Never block the user's work. The hook nudges; it doesn't refuse a call.

Tests

cd skills/agent-kit
uv run --script cost/scripts/agent_guard.py --selftest
uv run --script prompt-cache/scripts/pcache.py --self-test

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.