Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add tacoda/keystone-mcp --skill keystone-budget-reportergit clone --depth 1 https://github.com/tacoda/keystone-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tacoda/keystone-mcp/keystone-budget-reporter)<a href="https://agentmods.dev/skills/tacoda/keystone-mcp/keystone-budget-reporter"><img src="https://agentmods.dev/badge/skills/tacoda/keystone-mcp/keystone-budget-reporter/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tacoda/keystone-mcp/keystone-budget-reporter"><img src="https://agentmods.dev/badge/skills/tacoda/keystone-mcp/keystone-budget-reporter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.00441 |
| Opus 5 | $0.00008 | $0.00220 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
keystone-budget-reporter scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
keystone-budget-reporter
Read keystone://harness/budget and surface a digestible summary so
the user knows how many tokens their harness costs at session start.
The agent's ambient context includes every file it auto-loads at
session start — typically guides/, the menu file overlay, and the
project's iron-law + golden-rule sections. As the harness grows, this
cost grows. The budget reporter makes the growth visible.
When to use
- Periodic check (weekly, monthly).
- After a big learning sweep (audit promoted many findings to guides).
- When the user reports "the agent feels slow at session start".
Activities
-
Fetch the report. Read
keystone://harness/budget. -
Summarize totals.
Harness ambient-load budget ─────────────────────────── Total: <N files>, <W words>, ~<T tokens> Tokenizer: word_count (Phase 27 proxy) -
List hot files. Top 10 by word count, with port and approximate token cost:
Port File Words ~Tokens ---------- -------------------- ------ ------- playbooks task.md 410 547 sensors security-review.md 330 440 ... -
Per-port totals. Sorted by descending word count.
-
Cascade-excluded count (if non-zero). Project files shadowed by an upstream canonical lock — present on disk but never loaded. Propose deleting or relocating to recover the space.
Output
A markdown summary the user can paste into a discussion or attach to the next audit report. No state writes.
Iron laws
- Word-count is a proxy, not a tokenizer. Don't claim absolute token counts; surface the proxy explicitly.
- Don't suggest deleting hot files. Surface the cost; let the user decide which entries to prune.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 58 lines · 16 tokens per session scan A 838ccc20bf7c
keystone-budget-reporter is a skill published in the GitHub repository tacoda/keystone-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 441 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…