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/ronieneubauer/cli2mcp/claude-mdgit clone --depth 1 https://github.com/RonieNeubauer/cli2mcpWrote 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/ronieneubauer/cli2mcp/claude-md)<a href="https://agentmods.dev/instructions/ronieneubauer/cli2mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ronieneubauer/cli2mcp/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.01221 | $0.01221 |
| Opus 5 | $0.00611 | $0.00611 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
cli2mcp 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — cli2mcp
Project-level guidance for Claude Code sessions in this repo. English only everywhere.
Project at a glance
- Public OSS project under MIT, published to npm as
cli2mcp, repo on GitHub atRonieNeubauer/cli2mcp. - Stdio MCP server that wraps any CLI binary by parsing its
--helpoutput. Single package, no workspaces. - Anything you commit lands on a public branch — assume the world reads it.
Role
Claude is the sole executor: plans, writes code, tests, reviews its own diffs. Use the superpowers plugin workflow — brainstorming → writing-plans → test-driven-development → verification-before-completion — for any non-trivial change.
Local-only docs (gitignored)
The following live on disk but are NOT committed. Read them at session start for context, edit them locally as you work, but never re-add them to git:
CONTEXT.md— current status, pivot history, kill criteria, market positioning. Read first on cold session.TASKS.md— granular task list with checkboxes.CODEX.md— historical operating rules from when Codex was in the loop. Ignore as policy.prompts/— scratch prompts.
If CONTEXT.md or TASKS.md is missing locally, ask the user — do not recreate them from inference.
Session loop
- Read local
CONTEXT.mdfor current status (if present). rtk git log --oneline -20to see prior commits.- Check local
TASKS.mdfor the next unchecked item. - Before touching code on a new phase, invoke
superpowers:brainstormingif scope is unclear, orsuperpowers:writing-plansfor multi-step work. Skip both only for single-file, single-commit tasks already fully specified inTASKS.md. - Implement with
superpowers:test-driven-development— test first, then code. - Before claiming done, run
superpowers:verification-before-completion:pnpm test && pnpm typecheck && pnpm lint— all green, no exceptions. - Update local
TASKS.md(check boxes, add notes) and localCONTEXT.md## Statussection. - Commit (conventional commits, one logical change per commit).
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.
- 3d ago First seen · 96 lines · 1,221 tokens per session scan A efd5c3441653
cli2mcp CLAUDE.md is an instructions file published in the GitHub repository RonieNeubauer/cli2mcp (12 stars, last pushed 4mo ago), licensed MIT. It adds 1,221 tokens to every session, about $0.0061 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
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.
second-brain AGENTS.md
Instructions for LindaHaviv/second-brain, covering instructions for ai coding agents, what to read first, the rules (non-negotiable), common tasks, the sanctioned way and enforcement, not just instructions.