coograph: Command for Claude Code

.claude/commands/coograph-debug.md

coograph-debug is a command for Claude Code from paullukic/coograph. It costs 0 tokens per session (1,304 once invoked), scanned A, original, MIT.

A debugging command that investigates a bug or build error, identifies its root cause, and applies the smallest possible fix.

In plain words
What is it for?
Use it to reproduce and diagnose runtime bugs or build errors, then verify a targeted correction.
Why use it?
It focuses the investigation on recent and relevant code changes, reducing unnecessary edits while tracing the failure.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions AGENTS.md.

This is paullukic/coograph's own configuration. It tells Claude Code how to work on coograph itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything coograph configures →

Reuse

Borrowing it

Nothing to install: this file belongs to paullukic/coograph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/paullukic/coograph/main/.claude/commands/coograph-debug.md
Clone the repo
git clone --depth 1 https://github.com/paullukic/coograph

Made for: Claude Code.

Wrote 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.

agentmods badge for coograph-debug

README.md
[![agentmods](https://agentmods.dev/badge/commands/paullukic/coograph/coograph-debug/github.svg)](https://agentmods.dev/commands/paullukic/coograph/coograph-debug)
Your own site
<a href="https://agentmods.dev/commands/paullukic/coograph/coograph-debug"><img src="https://agentmods.dev/badge/commands/paullukic/coograph/coograph-debug/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.

agentmods 80×15 button for coograph-debug

Your own site · 80×15
<a href="https://agentmods.dev/commands/paullukic/coograph/coograph-debug"><img src="https://agentmods.dev/badge/commands/paullukic/coograph/coograph-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,304 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01304
Opus 5.5 $0.00000 $0.00522
Sonnet 5.5 $0.00000 $0.00261
Haiku 4.5 $0.00000 $0.00130

Measured 1mo ago against content hash c9c89478e067, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coograph-debug 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.

.claude/commands/coograph-debug.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Diagnose the bug or build error below. Find the root cause with minimal investigation, then apply the smallest possible fix.

Phase 0 — Orient with Code-Graph (MANDATORY — non-negotiable)

Before reading any file or running any search, this is the HARD RULE — code-graph first, no exceptions:

  1. Call get_minimal_context(task="debug <symptom>") then detect_changes(). ALWAYS start here. Use detect_changes() risk scores first — recent high-risk changes are the most likely culprit. Use the returned file list to focus investigation.
  2. Fall back to sqlite3 .code-graph/graph.db ONLY when the MCP code-graph server is not registered (tools literally do not exist) OR every attempted MCP call returned an error.
  3. Fall back to standard search/read tools ONLY when Step 1 AND Step 2 are both impossible because the code-graph DB is absent from the workspace.

"Slow", "unwieldy", "it's a simple bug" are NOT valid reasons to bypass. When tracing call chains use query_graph("callers_of", fn) and query_graph("callees_of", fn) before reading files. Validate every hypothesis directly in source regardless of graph output.

Protocol

For Runtime Bugs

  1. REPRODUCE: Can you trigger it reliably? What is the minimal reproduction? Consistent or intermittent?
  2. GATHER EVIDENCE (parallel when possible):
    • Read full error messages and stack traces — every word, not just the first line.
    • Check recent changes: git log --oneline -10, git blame on suspect lines.
    • Find working examples of similar code in the codebase.
    • Read the actual code at error locations.
  3. HYPOTHESIZE: Compare broken vs working code. Trace data flow from input to error. Document one hypothesis before investigating further. Identify what test would prove/disprove it.
  4. FIX: Apply ONE change. Predict the test that proves the fix. Check for the same pattern elsewhere.
  5. VERIFY: Run the failing test/build to confirm the fix works. Verify no regressions.

For Build/Compilation Errors

Read the full file on GitHub · 102 lines

Changes

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.

  1. 1mo ago Changed · +3 lines c9c89478e067
  2. 1mo ago Changed · +15 lines 9d9f1d6598a3
  3. 2mo ago First seen · 84 lines · 0 tokens per session scan A 1220147a90c9

Subscribe to this mod's changes

coograph-debug is a command published in the GitHub repository paullukic/coograph (17 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,304 tokens. 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.

Related

coograph-debug compared with commands from other repositories

coograph-debug next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
coograph-debugpaullukic/coographCommand1712d agoMITA0Claude Code
bootstraptravisjneuman/.claudeCommand107yesterdayMITC8Claude Code
health-checktravisjneuman/.claudeCommand107yesterdayMITC9Claude Code
performance-audithalflength-ampleness75/claude-code-recipesCommand223d agoMITA17Claude Code
debughalflength-ampleness75/claude-code-recipesCommand223d agoMITA16Claude Code
cg-senior-code-reviewakinalpfdn/claude-groundCommand1161mo agononeA97Claude Code
cg-indie-observabilityakinalpfdn/claude-groundCommand1161mo agononeB124Claude Code