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/vypdev/copilot/agents-mdgit clone --depth 1 https://github.com/vypdev/copilotWhat 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.00245 | $0.00245 |
| Opus 5 | $0.00122 | $0.00122 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
copilot 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.
This is a copy
100% identical to ols4 AGENTS.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
graphify
This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.
When the user types /graphify, use the installed graphify skill or instructions before doing anything else.
Rules:
- For codebase questions, first run
graphify query "<question>"when graphify-out/graph.json exists. Usegraphify path "<A>" "<B>"for relationships andgraphify explain "<concept>"for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output. - Dirty graphify-out/ files are expected after hooks or incremental updates; dirty graph files are not a reason to skip graphify. Only skip graphify if the task is about stale or incorrect graph output, or the user explicitly says not to use it.
- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
- After modifying code, run
graphify update .to keep the graph current (AST-only, no API cost).
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 · 13 lines · 245 tokens per session scan A 6a4a2e13159f
copilot AGENTS.md is an instructions file published in the GitHub repository vypdev/copilot (2 stars, last pushed yesterday), licensed MIT. It adds 245 tokens to every session, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ols4 AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
github-mcp-server copilot-instructions.md
Instructions for github/github-mcp-server, covering github mcp server - copilot instructions, project overview, critical build & validation steps, required commands (run before committing) and when modifying mcp tools/endpoints.
av CLAUDE.md
Instructions for aviator-co/av, covering claude.md, project overview, documentation sources, command structure philosophy and development workflow.
vscode-gitlens AGENTS.md
AGENTS.md instructions for gitkraken/vscode-gitlens, covering gitlens development guide, working style expectations, development environment, development commands and git & repository guidelines.
ghtkn AGENTS.md
Instructions for suzuki-shunsuke/ghtkn, a project described as: A CLI to create short-lived (8 hours) GitHub App User Access Token for secure local development.
vscode-gitlens CLAUDE.md
Claude Code instructions for gitkraken/vscode-gitlens, a project described as: Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via…
msaccess-vcs-addin AGENTS.md
AGENTS.md instructions for joyfullservice/msaccess-vcs-addin, covering project overview, repository structure, architecture overview, component diagram and key architectural patterns.