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/router-for-me/cliproxyapi/claude-mdgit clone --depth 1 https://github.com/router-for-me/CLIProxyAPIWrote 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/router-for-me/cliproxyapi/claude-md)<a href="https://agentmods.dev/instructions/router-for-me/cliproxyapi/claude-md"><img src="https://agentmods.dev/badge/instructions/router-for-me/cliproxyapi/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.00004 | $0.00004 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
CLIProxyAPI 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.
This is a copy
100% identical to deepseek-harness CLAUDE.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
@AGENTS.md
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 · 1 lines · 4 tokens per session scan A 918b1c905593
CLIProxyAPI CLAUDE.md is an instructions file published in the GitHub repository router-for-me/CLIProxyAPI (49,769 stars, last pushed 2d ago), licensed MIT. It adds 4 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
lobehub AGENTS.md
AGENTS.md instructions for lobehub/lobehub, covering lobehub development guidelines, tech stack, agent skills, project structure and spa routes and features.
opencodex AGENTS.md
AGENTS.md instructions for lidge-jun/opencodex, covering agents.md, what this project is, repository layout, optional subsystems stay off the core path and the devlog directory.
ClaudeBar CLAUDE.md
Claude Code instructions for tddworks/ClaudeBar, covering claude.md, project overview, build & test commands, quick start and install tuist (if not installed).
imagine-mcp AGENTS.md
AGENTS.md instructions for n24q02m/imagine-mcp, covering imagine-mcp, architecture, tool signatures, model selection and transport modes.
nodetool CLAUDE.md
Claude Code instructions for nodetool-ai/nodetool, a project described as: Agentic film production.
backchannel CLAUDE.md
Claude Code instructions for talberthoule/backchannel, covering claude.md, coordination record, current codebase snapshot, build & run and sentrux structural analysis.