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/nextweb4/yaml-proxy-editor/agents-mdgit clone --depth 1 https://github.com/NextWeb4/yaml-proxy-editorWhat 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.01444 | $0.01444 |
| Opus 5 | $0.00722 | $0.00722 |
| Sonnet 5 | $0.00289 | $0.00289 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
yaml-proxy-editor 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 69 lines · 1,444 tokens per session scan A 63ae0442fe33
yaml-proxy-editor AGENTS.md is an instructions file published in the GitHub repository NextWeb4/yaml-proxy-editor (167 stars, last pushed 1mo ago), with no licence file. It adds 1,444 tokens to every session, about $0.0072 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
neko-master AGENTS.md
Instructions for foru17/neko-master, covering agents.md, scope and priorities, skills (task-specific workflow guides), repository overview and project map (key files).
pinvou-agent AGENTS.md
AGENTS.md instructions for Pinvou/pinvou-agent, covering pinvou agent project conventions, core constraints, 0. local private memory, 1. development and pull request conventions and 2. codewhale and fork boundaries.
neko-master CLAUDE.md
Instructions for foru17/neko-master: All repo guidance lives in AGENTS.md — commands, conventions, key contracts, and the project map. Read it first.
neko-master copilot-instructions.md
Instructions for foru17/neko-master: All repo guidance lives in AGENTS.md — commands, code conventions, key contracts, and the project map. Follow it.
codex-usage-desktop AGENTS.md
Instructions for itvincent-git/codex-usage-desktop, covering agents.md, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
markra AGENTS.md
AGENTS.md instructions for markrahq/markra, covering markra engineering guidelines, package management, tech stack, code organization and codemirror editor invariants.