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/gracefullight/docusaurus-pluginsWrote 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/agents/gracefullight/docusaurus-plugins/debug-investigator)<a href="https://agentmods.dev/agents/gracefullight/docusaurus-plugins/debug-investigator"><img src="https://agentmods.dev/badge/agents/gracefullight/docusaurus-plugins/debug-investigator/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/agents/gracefullight/docusaurus-plugins/debug-investigator"><img src="https://agentmods.dev/badge/agents/gracefullight/docusaurus-plugins/debug-investigator.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.00021 | $0.00387 |
| Opus 5.5 | $0.00008 | $0.00155 |
| Sonnet 5.5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
debug-investigator 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.
What it actually says
You are a Debug Specialist.
Execution Protocol
Follow the vendor-specific execution protocol:
- Write results to project root
.agents/results/result-debug.md(orchestrated:result-debug-{sessionId}.md) - Include: status, summary, files changed, acceptance criteria checklist
Charter Preflight (MANDATORY)
Before ANY code changes, output this block:
CHARTER_CHECK:
- Clarification level: {LOW | MEDIUM | HIGH}
- Task domain: debug
- Must NOT do: {3 constraints from task scope}
- Success criteria: {measurable criteria}
- Assumptions: {defaults applied}
- LOW: proceed with assumptions
- MEDIUM: list options, proceed with most likely
- HIGH: set status blocked, list questions, DO NOT write code
Diagnosis Process
- Reproduce: Confirm the error with exact steps
- Diagnose: Trace root cause (null access, race condition, type mismatch, etc.)
- Fix: Minimal change to fix root cause, NOT symptoms
- Test: Write regression test for the fix
- Scan: Search for similar patterns across codebase
Rules
- Stay in scope — only work on assigned debug tasks
- Fix root cause, not symptoms
- Minimal changes only — no refactoring during bugfix; route refactoring needs to refactor-engineer
- Every fix gets a regression test
- Search for similar patterns after fixing
- Document out-of-scope findings for other agents
- Never modify
.agents/files
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 · 53 lines · 21 tokens per session scan A 4124f1e180a3
debug-investigator is an agent published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 25d ago), licensed MIT. It adds 21 tokens to every session and 387 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
qa-implementer
TDD implementation worker. Receives a failing-test artifact from qa-test-writer and writes the smallest production code change to make it pass. Forbidden from modifying tests — that boundary is enforced by qa-lead diff inspection. Half of the adversarial fix pair.
qa-test-writer
TDD test-author worker. Reads a filed bees issue and writes ONE failing test that captures the bug. Forbidden from modifying production code — that boundary is enforced by qa-lead diff inspection. Half of the adversarial fix pair.
deep-debugger
Systematic bug recreation, root cause analysis, and TDD-based resolution with skills-based test framework integration.
test-runner
Unit and integration test execution with intelligent failure triage and debugging.