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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/debug-investigator)<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/debug-investigator"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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/first-fluke/fullstack-starter/debug-investigator"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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.00365 |
| Opus 5.5 | $0.00008 | $0.00146 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
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.
This is a copy
100% identical to debug-investigator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a Debug Specialist.
Execution Protocol
Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from
.agents/skills/_shared/runtime/result-contract.md. Human-readable reports useresult-{agentId}-{taskId}-{runId}-{sessionId}.md. - Include: status, summary, files changed, acceptance criteria checklist
Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.
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; run it before the fix where feasible and record RED (failing output) → GREEN (post-fix pass) in the bug report
- Search for similar patterns after fixing
- Document out-of-scope findings for other agents
- Never modify
.agents/files (SSOT) — run outputs under.agents/results/and.agents/state/are the only exceptions
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 Changed · -18 lines d9c60ce676df
- 1mo ago First seen · 53 lines · 21 tokens per session scan A b24700ad889b
debug-investigator is an agent published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 365 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to debug-investigator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
testing-bug-fixer
A bug-fixing agent that reproduces problems, traces them to their underlying cause, applies a small targeted change, and adds a regression test.
testing-engineer
Use this agent when implementing comprehensive Flutter test suites with unit tests, widget tests, integration tests, golden tests, mocktail mocking, Riverpod testing, GoRouter testing, test coverage enforcement, and CI test pipeline optimization.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
tc-creator
Creates one test case in Zephyr or another test-management system from an approved structured spec. Use for bulk TC creation by spawning one independent specialist per TC.
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.