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 agentmods add skills/albatrossflyon-coder/claude-token-operator-kit/gaugenpx skills add albatrossflyon-coder/claude-token-operator-kit --skill gaugegit clone --depth 1 https://github.com/albatrossflyon-coder/claude-token-operator-kitWrote 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/albatrossflyon-coder/claude-token-operator-kit/gauge)<a href="https://agentmods.dev/skills/albatrossflyon-coder/claude-token-operator-kit/gauge"><img src="https://agentmods.dev/badge/skills/albatrossflyon-coder/claude-token-operator-kit/gauge.svg" alt="Measured on agentmods" 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.00063 | $0.00391 |
| Opus 5 | $0.00032 | $0.00196 |
| Sonnet 5 | $0.00013 | $0.00078 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
gauge 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 6d 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
Run the context gauge in snapshot mode and print the result inline.
Steps
-
Find the gauge script:
- Check
tools/cc-token-gauge/context_gauge.pyrelative to current working directory - Check
~/cc-token-gauge/context_gauge.py - If neither found: tell user it ships inside claude-token-operator-kit: clone that repo and run from its root
- Check
-
Run it with --once flag:
python "tools/cc-token-gauge/context_gauge.py" --once
-
Print the full dashboard output inline in the conversation.
-
Add one line of advice based on the output:
- Context > 80%: "Run /compact now."
- Messages > 30 + context > 50%: "Plan to /compact before next major task."
- Cache efficiency < 30%: "Low cache reuse: /compact will rebuild cache and cut costs."
- Otherwise: "Session healthy."
If Python Not Found
Tell the user:
Python not found. Run this in a terminal instead:
python "/path/to/claude-token-operator-kit/tools/cc-token-gauge/context_gauge.py" --once
Notes
- --once flag prints once and exits. No loop, no refresh.
- Auto-finds the active session JSONL: no path needed.
- Works in CC terminal and CC Desktop.
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.
- 6d ago First seen · 44 lines · 63 tokens per session scan A 7278f9ca2d07
gauge is a skill published in the GitHub repository albatrossflyon-coder/claude-token-operator-kit (5 stars, last pushed 17d ago), licensed MIT. It adds 63 tokens to every session and 391 once invoked, about $0.0003 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…