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/benchflow-ai/agents/copilot-instructionsgit clone --depth 1 https://github.com/benchflow-ai/agentsWhat 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.00378 | $0.00378 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
agents 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.
This is a copy
100% identical to mini-swe-agent copilot-instructions.md — 0 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
Style guide
- Target python 3.10 or higher
- Use python with type annotations. Use
listinstead ofList. - Use
pathlibinstead ofos.path. UsePath.read_text()overwith ...open()constructs. - Use
typerto add interfaces - Keep code comments to a minimum and only highlight particularly logically challenging things
- Do not append to the README unless specifically requested
- Use
jinjafor formatting templates - Use
dataclassfor keeping track config - Do not catch exceptions unless explicitly told to.
- Write concise, short, minimal code.
- Not every exception has to be caught. Exceptions are a good way to show problems to a user.
- This repository rewards minimal code. Try to be as concise as possible.
- Do NOT warn about print messages in tests, print statements in tests are OK!
Test style
- Use
pytest, notunittest. - Do not mock/patch anything that you're not explicitly asked to do
- Avoid writing trivial tests. Every test should test for at least one, preferably multiple points of failure
- Avoid splitting up code in multiple lines like this:
a=func()\n assert a=b. Instead, just doassert func() == b - The first argument to
pytest.mark.parametrizeshould be a tuple (not a string! not a list!), the second argument must be a list (not a tuple!). - Do NOT warn about print messages in tests, print statements in tests are OK!
Here's an example for rule 4:
# bad
result = func()
assert result == b
# good
assert func() == b
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 · 37 lines · 378 tokens per session scan A 6a868fc1a4fd
agents copilot-instructions.md is an instructions file published in the GitHub repository benchflow-ai/agents (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 378 tokens to every session, about $0.0019 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mini-swe-agent copilot-instructions.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
codeg AGENTS.md
AGENTS.md instructions for xintaofei/codeg, covering agents.md, 项目概述, 技术栈, 代码检查与测试(任务完成后进行必要的检查) and 前端.
golembot CLAUDE.md
Instructions for 0xranx/golembot, covering golembot — project conventions for claude code, architecture hard constraints, things you must never do, interface change rules and file responsibility boundaries.
pi-go CLAUDE.md
Instructions for dimetron/pi-go, covering claude.md — pi-go, work in a git worktree, not the primary checkout, where worktrees live, what pi-go's agent already does, and why it matters and commits: all commits must be signed.
peri CLAUDE.md
Instructions for KonghaYao/peri, covering claude.md — perihelion, 先读什么, 跨仓库契约, 任务路由 and 代码定位.
golembot AGENTS.md
Instructions for 0xranx/golembot, covering assistant context, installed skills, directory structure and conventions.
openinterpreter AGENTS.md
Instructions for openinterpreter/openinterpreter, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.