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 instructions/dark-hxx/cli-manager/claude-mdgit clone --depth 1 https://github.com/dark-hxx/CLI-ManagerWrote 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/instructions/dark-hxx/cli-manager/claude-md)<a href="https://agentmods.dev/instructions/dark-hxx/cli-manager/claude-md"><img src="https://agentmods.dev/badge/instructions/dark-hxx/cli-manager/claude-md.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 | $0.02663 | $0.02663 |
| Opus 5 | $0.01332 | $0.01332 |
| Sonnet 5 | $0.00533 | $0.00533 |
| Haiku 4.5 | $0.00266 | $0.00266 |
Grade A, and why
CLI-Manager CLAUDE.md 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 4d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 117 lines · 2,663 tokens per session scan A 80a89110678a
CLI-Manager CLAUDE.md is an instructions file published in the GitHub repository dark-hxx/CLI-Manager (709 stars, last pushed 5d ago), licensed AGPL-3.0. It adds 2,663 tokens to every session, about $0.0133 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 instructions, from other repositories
gemini-cli-hud GEMINI.md
Instructions for yideng-xl/gemini-cli-hud, covering gemini cli hud, what it shows, how it works and notes.
gemini-cli-hud AGENTS.md
Instructions for yideng-xl/gemini-cli-hud: This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in nodemodules/next/dist/docs/ before writing any code. Heed deprecation notices.
gemini-cli-hud CLAUDE.md
Instructions for yideng-xl/gemini-cli-hud, a project described as: Real-time bottom-sticky HUD for Gemini CLI — model, context usage, tool calls, and more.
agent-of-empires AGENTS.md
AGENTS.md instructions for agent-of-empires/agent-of-empires, covering repository guidelines, where to look, commands, code rules and tests.
terminal-browser AGENTS.md
AGENTS.md instructions for zenbu-labs/terminal-browser, a project described as: A browser inside your terminal.
obsidian-claude-sidebar CLAUDE.md
Instructions for derek-larson14/obsidian-claude-sidebar, covering claude sidebar - agent guide, what this plugin does, two things you can help the user do, step 1: diagnose and step 2a: file a bug report.