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/agent-next/agent-ready/copilot-instructionsgit clone --depth 1 https://github.com/agent-next/agent-readyWhat 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.00168 | $0.00168 |
| Opus 5 | $0.00084 | $0.00084 |
| Sonnet 5 | $0.00034 | $0.00034 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
agent-ready copilot-instructions.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.
What it actually says
TypeScript project using Node 20+ with strict mode enabled.
Commands: npm test (152 tests), npm run check (typecheck + lint + format), npm run build (tsc).
Code style: kebab-case files, PascalCase interfaces, camelCase functions. Interfaces over types. Avoid any, use unknown. Export types from src/types.ts.
Testing: Node built-in test runner via tsx --test. Fixtures in test/fixtures/. Always run tests after changes and update tests in the same pass as code changes.
Git: Atomic commits with semantic prefixes (feat/fix/docs/chore). Run npm run check before committing.
Do not add external API calls — all scanning must remain local. Do not modify src/types.ts without updating all consumers.
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 · 12 lines · 168 tokens per session scan A 914815fcc564
agent-ready copilot-instructions.md is an instructions file published in the GitHub repository agent-next/agent-ready (27 stars, last pushed 3mo ago), licensed MIT. It adds 168 tokens to every session, about $0.0008 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
deer-flow copilot-instructions.md
Copilot instructions for bytedance/deer-flow, covering copilot onboarding instructions for deerflow, 1) repository summary, 2) runtime and toolchain requirements, 3) build/test/lint/run - verified command sequences and a. bootstrap and install.
LeAgent AGENTS.md
Instructions for vixues/LeAgent, covering leagent development guidelines, project overview, architecture, execution topology (one kernel, many ingresses) and surface map (where things live).
learn-opencode-agent CLAUDE.md
Instructions for qqzhangyanhua/learn-opencode-agent, covering claude.md, 项目定位, 架构总览, 模块结构图 and 模块索引.
open-vibe-island AGENTS.md
AGENTS.md instructions for Octane0411/open-vibe-island, covering agents, goal, required workflow, commit policy and safety rules.
codehydra CLAUDE.md
Instructions for stefanhoelzl/codehydra, covering claude.md, critical rules, no ignore comments, api/ipc interface changes and new boundary interfaces.
sprawling CLAUDE.md
Instructions for 2youg1/sprawling: See AGENTS.md. It is the whole instruction set for this repository — the loop, what to read first, the five steps of one change, the rules a machine holds, and the language and commit conventions.