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/jer-y/copilot-proxy/agents-mdgit clone --depth 1 https://github.com/Jer-y/copilot-proxyWhat 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.02805 | $0.02805 |
| Opus 5 | $0.01403 | $0.01403 |
| Sonnet 5 | $0.00561 | $0.00561 |
| Haiku 4.5 | $0.00281 | $0.00281 |
Grade A, and why
copilot-proxy 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Top-Level Engineering Principle
- Avoid over-engineering. Choose the simplest complete solution that satisfies the current confirmed requirement and preserves the existing product contract.
- Complexity must be earned by a concrete current need, observed evidence, or a real second use case. Hypothetical future flexibility, practically unreachable edge cases, and architectural elegance alone are not sufficient justification.
- This principle governs architecture, implementation, debugging, testing, review, documentation, and operations. Unless correctness, security, an external protocol contract, or an explicit user requirement demands otherwise, prefer narrower scope, fewer moving parts, and reversible changes over broader or more generic designs.
Build, Lint, and Test Commands
- Core:
bun run build,bun run dev,bun run start,bun run lint,bun run lint --fix,bun run typecheck,bun run knip, andbun run audit. - Tests:
bun test,bun run test:coverage, orbun test <test-file>. - Common targeted tests:
tests/create-responses.test.ts,tests/messages-routing.test.ts,tests/model-config.test.ts,tests/copilot-auth-recovery.test.ts,tests/auth-recovery-routes.test.ts,tests/concurrency-limiter.test.ts, andtests/request-signal-regression.test.ts. - Protocol and live gates: use
bun run test:node:http,bun run test:live:copilot,bun run test:live:responses-item-replay, andbun run test:live:codexas applicable. Exact environment variables, route matrices, and acceptance criteria live in the capability validation guide. - Native service:
bun run ./src/main.ts enable; usestop,restart,status, andlogsfor lifecycle control. Linux boot-before-login requires systemd user lingering. The removedstart -dpath must continue to direct users toenable. - Other CLI subcommands:
setup,models,doctor,auth,check-usage, anddebug. - Codex setup policy:
Before authentication, inspect the installed Codex version and bundled catalog. Require Codex 0.134.0 or newer, and apply the same usable bundled-metadata gate to interactive choices and explicit
--model. Keep live route-probe evidence separate from evidence that the generated profile was saved and executed with real Codex; setup does not provide the latter.
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.
- 2d ago First seen · 79 lines · 2,805 tokens per session scan A b5df9db1d34b
copilot-proxy AGENTS.md is an instructions file published in the GitHub repository Jer-y/copilot-proxy (37 stars, last pushed 8d ago), licensed MIT. It adds 2,805 tokens to every session, about $0.0140 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
copilot-proxy-api CLAUDE.md
Instructions for voidsteed/copilot-proxy-api, covering claude.md, project overview, common commands, architecture and entry points & cli structure.
airelay CLAUDE.md
Claude Code instructions for ligj1706/airelay, covering claude.md, 项目概述, 产品定位, 设计原则 and 产品演进方向.
ccNexus AGENTS.md
AGENTS.md instructions for jackychanisnotme/ccNexus, covering agents.md, 项目概述, 当前产品阶段与最高优先级, 存量客户兼容性规则 and 未来服务器运营功能设计边界.
ccNexus CLAUDE.md
Claude Code instructions for jackychanisnotme/ccNexus, covering claude.md, 项目概述, 常用开发命令, 开发与构建 and 桌面应用开发模式(支持热重载).
copilot-proxy-api AGENTS.md
Instructions for voidsteed/copilot-proxy-api, covering agents.md, build, lint, and test commands and code style guidelines.
apm python.instructions.md
Python development guidelines.