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/tae2089/code-context-graph/agents-mdgit clone --depth 1 https://github.com/tae2089/code-context-graphWhat 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.02500 | $0.02500 |
| Opus 5 | $0.01250 | $0.01250 |
| Sonnet 5 | $0.00500 | $0.00500 |
| Haiku 4.5 | $0.00250 | $0.00250 |
Grade A, and why
code-context-graph 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 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-context-graph
A local code analysis tool that parses codebases with Tree-sitter and builds a knowledge graph.
MCP Server
The ccg MCP server registered in .mcp.json provides 18 tools:
parse_project,build_or_update_graph,run_postprocessget_node,search,describe,query_graph,list_graph_stats,list_namespaces,get_minimal_contextget_impact_radius,trace_flow,list_cross_refsdetect_changes,get_affected_flows,list_flowsget_annotationget_doc_content
ccg serve is the local stdio MCP entry point. Self-hosted HTTP mode is provided by
the separate ccg-server binary, which serves /mcp, /health, /ready, /status,
and /webhook.
Webhooks are enabled in ccg-server when allowed repositories are configured with the --allow-repo flag.
Per-repository branch filtering: --allow-repo "org/api:main,develop" (glob patterns; defaults to main/master when omitted).
Compatible with GitHub (X-Hub-Signature-256) and Gitea (X-Gitea-Signature, X-Gitea-Event).
Push event pipeline: receive push event -> automatic clone/pull -> graph build -> DB persistence.
Graceful shutdown: SIGINT/SIGTERM propagates context cancellation to in-progress clone/build work.
Agent Skills (7)
| Skill | Description |
|---|---|
/ccg |
Fast read-only discovery and targeted source verification |
/ccg-search-verify |
Absence, completeness, and exhaustive search verification |
/ccg-build |
Explicit-only graph build, update, migrate, and postprocess |
/ccg-analyze |
Explicit-only impact, flow tracing, and change-risk analysis |
/ccg-annotate |
Annotation system: AI annotation workflow and tag reference |
/ccg-docs |
Documentation: generation, DB-backed discovery, and lint |
/ccg-namespace |
Namespace isolation for multi-project graph data |
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 · 158 lines · 2,500 tokens per session scan A 91530bcd3590
code-context-graph AGENTS.md is an instructions file published in the GitHub repository tae2089/code-context-graph (17 stars, last pushed 11d ago), licensed MIT. It adds 2,500 tokens to every session, about $0.0125 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-30.
Other instructions, from other repositories
ollama AGENTS.md
Instructions for ollama/ollama, covering agents.md and building.
go-micro CLAUDE.md
Instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
ollama CLAUDE.md
Instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
sq AGENTS.md
Instructions for neilotoole/sq, covering agents.md, about sq, key documents, common commands and conventions.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.