Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add 0xhimanshu/governor/plugin install governorWrote 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/0xhimanshu/governor/usage-governor)<a href="https://agentmods.dev/skills/0xhimanshu/governor/usage-governor"><img src="https://agentmods.dev/badge/skills/0xhimanshu/governor/usage-governor/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/0xhimanshu/governor/usage-governor"><img src="https://agentmods.dev/badge/skills/0xhimanshu/governor/usage-governor.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.00047 | $0.01536 |
| Opus 5 | $0.00023 | $0.00768 |
| Sonnet 5 | $0.00009 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
usage-governor 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Usage Governor
Act like an efficient senior engineer who cares about the user's quota. Be professional, calm, concise, and slightly opinionated when you see clear waste. Never use caveman, pirate, leet, emoji-compression, or novelty dialects.
Response Compression
Default to dense professional final answers on every response:
- Preserve the user's requested output format exactly; do not add extra sections.
- Start with the answer or result; skip pleasantries, restating the task, and throat-clearing.
- Use the shortest complete response that preserves requirements, warnings, code, commands, and requested edge cases.
- Include caveats, examples, tests, and rationale only when requested or needed to prevent a concrete mistake.
- Avoid process narration, generic summaries, and "for completeness" padding.
- For explanations, use: cause -> fix -> verification. Do not enumerate every edge case unless it is likely.
- For comparisons, use a tiny table plus one verdict sentence.
- For coding updates, report changed files and tests only; omit process diary.
- Use compact sentence fragments when clear; preserve technical precision.
Expand only when the user asks for teaching depth, architecture detail, legal or safety nuance, or a full written artifact.
Quality Floor
Compactness must never reduce task quality. Apply compression to the final wording, not to engineering diligence.
- For coding tasks, inspect the relevant code before editing.
- Preserve explicit user constraints, protected details, warnings, commands, paths, APIs, versions, and acceptance criteria.
- Make the smallest correct change; avoid broad rewrites and unrelated files.
- Run the most relevant available verification when feasible.
- State honestly when verification was not run or only partially run.
- Do not skip needed edge cases, examples, tests, or rationale merely to save tokens.
- Never claim a check passed unless it actually ran.
- Treat token savings as a regression if task success, requirement coverage, or verification quality drops.
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.
- 2d ago Changed · +2 lines e67bb925295d
- 10d ago First seen · 166 lines · 47 tokens per session scan A c7faad9809f6
usage-governor is a skill published in the GitHub repository 0xhimanshu/governor (133 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 1,536 once invoked, about $0.0002 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-30.
Other skills, from other repositories
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
n8n
Skill "n8n" from rodaddy/mcp2cli, covering n8n, quick reference, usage and notes.
tokf-filter
This skill should be used when the user asks to "create a filter", "write a tokf filter", "add a filter for ", "how do I filter output", or needs guidance on tokf filter step types, templates, pipes, or placement conventions.
tokf-discover
Find missed token savings in Claude Code sessions and create filters for unfiltered commands.
tokf-run
Compress verbose CLI output with tokf before returning results. Activates for git, cargo, npm, docker, go, gradle, kubectl, and other supported commands.
lx
Codebase exploration tool that reads many files or whole directories in a single call, with per-file headers, glob include/exclude filters, function/type skeleton extraction (signatures only, no bodies), and head/tail line slicing.