debugger

A software debugging assistant for investigating errors, logs, execution paths, performance problems, failing tests, and deployment issues. It uses symptoms and evidence to trace events to a likely root cause.

In plain words
What is it for?
Use it to diagnose production incidents, analyze CI/CD or application logs, trace execution flows, find performance bottlenecks, investigate database queries, and troubleshoot tests or deployments.
Why use it?
It replaces scattered troubleshooting with a structured investigation that tests hypotheses against logs, metrics, stack traces, and code behavior. It also separates immediate fixes from ways to prevent recurrence.

Agent

Install

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.

agentmods
npx agentmods add agents/ihatesea69/kiro-kit/debugger
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00034 $0.00315
Opus 5 $0.00017 $0.00158
Sonnet 5 $0.00007 $0.00063
Haiku 4.5 $0.00003 $0.00032

Measured yesterday against content hash d38c06036520, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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.

.kiro/agents/debugger.md · 41 lines

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

  1. Gather symptoms, error messages, and affected timeframes
  2. Collect relevant logs, metrics, and stack traces
  3. Correlate events across different sources
  4. Form hypotheses and validate with evidence
  5. Identify root cause through systematic elimination
  6. 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
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. yesterday First seen · 41 lines · 34 tokens per session scan A d38c06036520

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 12d ago), licensed MIT. It adds 34 tokens to every session and 315 once invoked, about $0.0002 per session on Opus 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.