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.
git clone --depth 1 https://github.com/mtrdesign/whygraphWrote 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/rules/mtrdesign/whygraph/whygraph-codegraph)<a href="https://agentmods.dev/rules/mtrdesign/whygraph/whygraph-codegraph"><img src="https://agentmods.dev/badge/rules/mtrdesign/whygraph/whygraph-codegraph/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/mtrdesign/whygraph/whygraph-codegraph"><img src="https://agentmods.dev/badge/rules/mtrdesign/whygraph/whygraph-codegraph.svg" alt="Reviewed on agentmods" width="80" 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.00405 | $0.00405 |
| Opus 5.5 | $0.00162 | $0.00162 |
| Sonnet 5.5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
whygraph-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 15d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 15d ago Changed · +10 tokens per session 6783e74441a9
- 1mo ago First seen · 28 lines · 395 tokens per session scan A a36a30aa5789
whygraph-codegraph is a cursor rule published in the GitHub repository mtrdesign/whygraph (4 stars, last pushed 4d ago), with no licence file. It adds 405 tokens to every session, about $0.0016 per session on Opus 5.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 cursor rules, from other repositories
debugging
Debugging guidance for the Lineai MCP Server.
logging-standards
Use the Operative Control Center logging system instead of print statements.
optimized-workflow-level1
Optimized Level 1 workflow for quick bug fixes with token efficiency.
workflow-level1
Streamlined workflow for Level 1 Quick Bug Fix tasks.
codegraph
CodeGraph MCP usage guide — when to use which tool.
debugging-troubleshooting
Cursor rule "debugging-troubleshooting" from lazylagom/context-compose-mcp, covering debugging and troubleshooting guide, general debugging strategies, logging and console output, typescript type errors and mcp server debugging.