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/codegraph-ai/codegraph-rules-for-agents/copilot-instructionsgit clone --depth 1 https://github.com/codegraph-ai/codegraph-rules-for-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.00567 | $0.00567 |
| Opus 5 | $0.00283 | $0.00283 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
codegraph-rules-for-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 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeGraph — local code intelligence
This project has CodeGraph installed — a persistent semantic code graph with 42 MCP tools. It resolves references, so "who calls X?" is a single tool call, not multi-file grep.
Top 5 tools (use these first)
| When you need | Call this | NOT this |
|---|---|---|
| Who calls function X? | codegraph_get_callers |
grep for the function name |
| What breaks if I change X? | codegraph_analyze_impact |
reading every importing file |
| Context for editing a file | codegraph_get_edit_context |
reading 5+ files manually |
| Find a symbol by name | codegraph_symbol_search |
grep -r across the project |
| Module structure overview | codegraph_get_module_summary |
ls + reading each file |
URI format: file:///absolute/path. Use paths from symbol_search results directly.
Compact mode: pass compact: true for shorter output when scanning.
Common workflows
- PR review:
codegraph_pr_context— one call gives blast radius, test gaps, stale docs, reviewers - Refactoring:
symbol_search→analyze_impact→get_edit_context - Bug triage:
search_by_error→get_callers→get_ai_context(intent: "debug") - Onboarding:
get_module_summary→find_entry_points→get_call_graph
Decision rule
- Structural question? (callers, deps, impact) → codegraph tools
- Text question? (exact string, regex) → grep/read
- Not sure? → Try
codegraph_symbol_searchfirst. Empty → runcodegraph_reindex_workspace.
More tools
PR review: pr_context (blast radius, test gaps, stale docs, commit hint, reviewers)
Navigation: get_callees, get_call_graph, get_dependency_graph, traverse_graph, find_by_imports, find_entry_points
Quality: analyze_complexity, find_hot_paths, find_circular_deps, find_dead_imports
Docs: index_markdown, search_docs, verify_design, design_gaps, generate_architecture_doc
Memory: memory_store (pass agentSource: "copilot"), memory_search, memory_context
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 · 42 lines · 567 tokens per session scan A 35b09791eafd
codegraph-rules-for-agents copilot-instructions.md is an instructions file published in the GitHub repository codegraph-ai/codegraph-rules-for-agents (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 567 tokens to every session, about $0.0028 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.