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/agents-mdgit clone --depth 1 https://github.com/router-for-me/CLIProxyAPIWhat 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.01058 | $0.01058 |
| Opus 5 | $0.00529 | $0.00529 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
CLIProxyAPI AGENTS.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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ProxyPilot AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Go 1.26+ proxy server providing OpenAI/Gemini/Claude/Codex compatible APIs with OAuth and round-robin load balancing.
Repository
Commands
gofmt -w . # Format (required after Go changes)
go build -o cli-proxy-api ./cmd/server # Build
go run ./cmd/server # Run dev server
go test ./... # Run all tests
go test -v -run TestName ./path/to/pkg # Run single test
go build -o test-output ./cmd/server && rm test-output # Verify compile (REQUIRED after changes)
- Common flags:
--config <path>,--tui,--standalone,--local-model,--no-browser,--oauth-callback-port <port>
Config
- Default config:
config.yaml(template:config.example.yaml) .envis auto-loaded from the working directory- Auth material defaults under
auths/ - Storage backends: file-based default; optional Postgres/git/object store (
PGSTORE_*,GITSTORE_*,OBJECTSTORE_*)
Architecture
cmd/server/— Server entrypointinternal/api/— Gin HTTP API (routes, middleware, modules)internal/api/modules/amp/— Amp integration (Amp-style routes + reverse proxy)internal/thinking/— Main thinking/reasoning pipeline.ApplyThinking()(apply.go) parses suffixes (suffix.go, suffix overrides body), normalizes config to canonicalThinkingConfig(types.go), normalizes and validates centrally (validate.go/convert.go), then applies provider-specific output viaProviderApplier. Do not break this "canonical representation → per-provider translation" architecture.internal/runtime/executor/— Per-provider runtime executors (incl. Codex WebSocket)internal/translator/— Provider protocol translators (and sharedcommon)internal/registry/— Model registry + remote updater (StartModelsUpdater);--local-modeldisables remote updatesinternal/store/— Storage implementations and secret resolutioninternal/managementasset/— Config snapshots and management assetsinternal/cache/— Request signature cachinginternal/watcher/— Config hot-reload and watchersinternal/wsrelay/— WebSocket relay sessionsinternal/usage/— Usage and token accountinginternal/tui/— Bubbletea terminal UI (--tui,--standalone)sdk/cliproxy/— Embeddable SDK entry (service/builder/watchers/pipeline)test/— Cross-module integration tests
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.
- yesterday First seen · 59 lines · 1,058 tokens per session scan A a01f8eb7ece7
CLIProxyAPI AGENTS.md is an instructions file published in the GitHub repository router-for-me/CLIProxyAPI (49,373 stars, last pushed 2d ago), licensed MIT. It adds 1,058 tokens to every session, about $0.0053 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
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
antigravity-claude-proxy CLAUDE.md
Instructions for badrisnarayanan/antigravity-claude-proxy, covering claude.md, commands and non-obvious things.
neo-chat AGENTS.md
Instructions for u14app/neo-chat, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
proxypal AGENTS.md
Instructions for heyhuynhgiabuu/proxypal, covering proxypal, stack, structure, commands and code style.
ima2-gen AGENTS.md
Instructions for lidge-jun/ima2-gen, covering ima2-gen — ai context, what this project does, tech stack, project structure and agent skills (packaged).
opencodex 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.