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 agents/codegraph-ai/codegraph-rules-for-agents/codegraphgit 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.00037 | $0.01219 |
| Opus 5 | $0.00018 | $0.00609 |
| Sonnet 5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
codegraph 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeGraph — local code intelligence
CodeGraph maintains a persistent semantic graph of your codebase (functions, classes, imports, call edges, dependency edges) in RocksDB. It resolves references — so "who calls X?" is a single tool call, not a multi-file grep.
First time in this project?
Run codegraph_reindex_workspace once. Takes 5-30 seconds. After that, the index persists across sessions automatically and updates incrementally.
Start here — the 5 tools you'll use 90% of the time
| When you need | Call this | NOT this |
|---|---|---|
| Who calls function X? | codegraph_get_callers(uri, line) |
grep for the function name |
| What breaks if I change X? | codegraph_analyze_impact(uri, line) |
reading every importing file |
| Context for editing a file | codegraph_get_edit_context(uri, line) |
reading 5+ files manually |
| Find a symbol by name | codegraph_symbol_search(query) |
grep -r across the project |
| Module structure overview | codegraph_get_module_summary(directory) |
ls + reading each file |
These tools return resolved references (not string matches) — they know that auth::validate in file A calls jwt::verify in file B, even if the name doesn't appear as a literal string.
URI format: file:///absolute/path (not relative). Use the paths from symbol_search results directly.
Compact mode: most tools accept compact: true for shorter output. Use compact for scanning, full for deep investigation.
Common workflows (chain tools for best results)
- PR review:
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 - Design check:
index_markdown→verify_design→design_gaps
Decision rule
Before using Grep or reading multiple files for a code-structural question:
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 · 73 lines · 37 tokens per session scan A 2a02d296cbf4
codegraph is an agent published in the GitHub repository codegraph-ai/codegraph-rules-for-agents (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,219 once invoked, 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.