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/lzehrung/codegraph/copilot-instructionsgit clone --depth 1 https://github.com/lzehrung/codegraphWhat 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.00032 | $0.00032 |
| Opus 5 | $0.00016 | $0.00016 |
| Sonnet 5 | $0.00006 | $0.00006 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
codegraph 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
Copilot instructions
This repository keeps a single source of development guidance. Follow AGENTS.md:
AGENTS.md
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 · 5 lines · 32 tokens per session scan A 0255eff4d333
codegraph copilot-instructions.md is an instructions file published in the GitHub repository lzehrung/codegraph (4 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session, about $0.0002 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-31.
Other instructions, from other repositories
astra-code-map AGENTS.md
Instructions for SourceAstra/astra-code-map, covering repository guidelines, 项目结构, 构建、测试与开发, 代码风格与命名 and 测试指南.
mirage CLAUDE.md
Instructions for strukto-ai/mirage, covering claude.md, repo layout, typescript packages, python/typescript parity and module layout.
mcp-steroid CLAUDE.md
Instructions for jonnyzzz/mcp-steroid, covering claude.md, agents.md, design philosophy, recursive context lookup (do this before sub-folder work), sub-folder guides and must do.
TakoVM CLAUDE.md
Instructions for Tako-Research/TakoVM, covering tako vm, why gvisor?, architecture, key concepts and build & test.
tree-sitter-analyzer CLAUDE.md
Instructions for aimasteracc/tree-sitter-analyzer, covering ruflo — claude code configuration, rules, test quality rules — locked (2026-06-28), t-1: no new test files for existing plugins (blocker) and t-2: no weak assertions — ratchet-enforced (blocker).
tree-sitter-fsharp AGENTS.md
Instructions for ionide/tree-sitter-fsharp, covering improving the f# tree-sitter parser, project structure, running the cli, workflow for adding a new feature and 1. create a test case first.