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 commands/0xhimanshu/governor/install-rulesgit clone --depth 1 https://github.com/0xhimanshu/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/commands/0xhimanshu/governor/install-rules)<a href="https://agentmods.dev/commands/0xhimanshu/governor/install-rules"><img src="https://agentmods.dev/badge/commands/0xhimanshu/governor/install-rules.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.00024 | $0.00164 |
| Opus 5 | $0.00012 | $0.00082 |
| Sonnet 5 | $0.00005 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
install-rules 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 5d 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
Governor Install Rules
Install always-on compact professional rule snippets into a project.
Usage examples:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/install_rules.py" --project . --agents all
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/install_rules.py" --project . --agents codex,cursor
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/install_rules.py" --project . --agents all --force
Explain that these rule files provide compact response behavior for other agents. They do not install Claude Code telemetry, hooks, statusline, or Bash output filtering outside Claude Code.
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.
- 5d ago First seen · 21 lines · 24 tokens per session scan A a86b20ec5d47
install-rules is a command published in the GitHub repository 0xhimanshu/governor (133 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 164 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-30.
Other commands, from other repositories
benchmark
Run a TAU-bench evaluation end-to-end and present results.
list-branches
List project branches with their worktree status.
remove-branch
Remove a branch and its associated worktree.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
generate-rfcs
Break the PRD into sequential implementation RFCs.
test-strategy
Generate a test plan from features and RFCs.