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/0xjcf/MCP_CodeAnalysisWrote 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/0xjcf/mcp_codeanalysis/debug_history)<a href="https://agentmods.dev/rules/0xjcf/mcp_codeanalysis/debug_history"><img src="https://agentmods.dev/badge/rules/0xjcf/mcp_codeanalysis/debug_history/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/0xjcf/mcp_codeanalysis/debug_history"><img src="https://agentmods.dev/badge/rules/0xjcf/mcp_codeanalysis/debug_history.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.00143 | $0.00143 |
| Opus 5.5 | $0.00057 | $0.00057 |
| Sonnet 5.5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
debug_history 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 1mo 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.
- 1mo ago First seen · 18 lines · 143 tokens per session scan A 19f051959bea
debug_history is a cursor rule published in the GitHub repository 0xjcf/MCP_CodeAnalysis (7 stars, last pushed 9mo ago), with no licence file. It adds 143 tokens to every session, about $0.0006 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
misakanet-failure-memory
Search MisakaNet failure-memory before debugging common errors.
memorywhale
Query and write durable debugging memory recorded by MemoryWhale. Use when a build/test/deploy is failing and might have failed before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix…
debug-capture-pipeline
Debug llm-wiki-memory capture/recall — flush breadcrumbs, daily-vs-compile lag, failed-distill stash recovery, embedding cache, hook wiring. Use when memory didn't capture, doesn't recall, or a hook/cron looks broken.
synapse
Rules for using Synapse MCP — prefer the graph over grep.
memory-informed-debug
Use when diagnosing bugs, errors, failing tests, or crashes — consult prior debug outcomes and capture root causes in-flight.
moth
Use Moth for error analysis and verified fix memory.