Borrowing it
Nothing to install: this file belongs to imMamdouhaboammar/get-things-done. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/imMamdouhaboammar/get-things-done/main/.github/instructions/code-review-graph.instructions.mdgit clone --depth 1 https://github.com/imMamdouhaboammar/get-things-doneWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/immamdouhaboammar/get-things-done/code-review-graph)<a href="https://agentmods.dev/instructions/immamdouhaboammar/get-things-done/code-review-graph"><img src="https://agentmods.dev/badge/instructions/immamdouhaboammar/get-things-done/code-review-graph.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
get-things-done code-review-graph.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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Tools: code-review-graph
This project has a knowledge graph. Start with the code-review-graph MCP tools to narrow scope, then read the source. The graph is cheaper than scanning files and gives you structural context (callers, dependents, test coverage) that file search cannot.
When to use graph tools FIRST
- Exploring code:
semantic_search_nodes_toolorquery_graph_tool - Understanding impact:
get_impact_radius_tool - Code review:
detect_changes_tool+get_review_context_tool - Finding relationships:
query_graph_toolcallers_of/callees_of - Architecture questions:
get_architecture_overview_tool
Verify in the source
- Narrow scope with the graph, then read the source. Do not change code from graph output alone.
- For any non-trivial change, read the implementation and the relevant tests before concluding.
- Verify the exact source when touching behavior, database logic, migrations, retries, fallbacks, recovery, or compatibility code.
- When the graph and the source disagree, the source wins. The graph may be stale or may not model that relationship.
- An empty graph result can mean "not indexed" or "not statically visible", not "does not exist".
Key Tools
| Tool | Use when |
|---|---|
detect_changes_tool |
Risk-scored change analysis |
get_review_context_tool |
Token-efficient source snippets |
get_impact_radius_tool |
Blast radius of a change |
get_affected_flows_tool |
Impacted execution paths |
query_graph_tool |
Trace callers, callees, imports, tests |
semantic_search_nodes_tool |
Find functions/classes by keyword |
get_architecture_overview_tool |
High-level structure |
refactor_tool |
Rename planning, dead code |
Workflow
- The graph auto-updates on file changes (via hooks).
- Use
detect_changes_toolfor code review. - Use
get_affected_flows_toolto understand impact. - Use
query_graph_toolpattern="tests_for" to check coverage.
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 · 53 lines · 517 tokens per session scan A fdd9ac46ae5a
get-things-done code-review-graph.instructions.md is an instructions file published in the GitHub repository imMamdouhaboammar/get-things-done (2 stars, last pushed 5d ago), licensed MIT. It adds 517 tokens to every session, about $0.0026 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-09-05.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
vscode buildNext.instructions.md
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).
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).
langchain AGENTS.md
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.
spec-kit AGENTS.md
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.