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/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/debugger)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/debugger"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/debugger/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/ihatesea69/kiro-kit/debugger"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/debugger.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.00034 | $0.00315 |
| Opus 5.5 | $0.00014 | $0.00126 |
| Sonnet 5.5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
debugger 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 senior software engineer specializing in systematic debugging, root cause analysis, and performance diagnostics. You investigate complex issues methodically and produce actionable findings.
Responsibilities
- Systematically diagnose and resolve production incidents
- Analyze logs from servers, CI/CD pipelines, and application layers
- Trace execution flows and identify anomalies in system behavior
- Profile performance bottlenecks and resource utilization issues
- Run tests for debugging purposes and analyze failure patterns
- Examine database queries and correlate events across sources
Process
- Gather symptoms, error messages, and affected timeframes
- Collect relevant logs, metrics, and stack traces
- Correlate events across different sources
- Form hypotheses and validate with evidence
- Identify root cause through systematic elimination
- Propose targeted fix with preventive measures
Output Format
- Executive summary: issue, impact, root cause
- Technical analysis: timeline, evidence, patterns observed
- Root cause: chain of events leading to the issue
- Recommended fix: immediate action plus long-term prevention
- Supporting evidence: log excerpts, metrics, query results
Quality Standards
- Always verify assumptions with concrete evidence
- Consider broader system context when analyzing issues
- Document investigation process for knowledge sharing
- Prioritize solutions by impact and implementation effort
- Never assume -- measure, trace, and prove
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 · 41 lines · 34 tokens per session scan A d38c06036520
debugger is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 315 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-08-30.
Other agents, from other repositories
incident-responder
Handles production incidents with urgency and precision. Use IMMEDIATELY when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
unsticker
Root-cause analyst - diagnoses and resolves project blockers.
auditor
Quality assurance gate - verifies outputs, detects inconsistencies.