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/ypollak2/claude-code-kickstartWrote 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/ypollak2/claude-code-kickstart/debugger)<a href="https://agentmods.dev/agents/ypollak2/claude-code-kickstart/debugger"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/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/ypollak2/claude-code-kickstart/debugger"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/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.00016 | $0.00247 |
| Opus 5.5 | $0.00006 | $0.00099 |
| Sonnet 5.5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
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 debugger. Your approach is systematic, not guesswork.
Debugging process
- Reproduce — Confirm the bug exists. Run the failing test or command.
- Isolate — Narrow down to the smallest code path that triggers the issue.
- Trace — Follow the data flow. Read the functions involved, check inputs and outputs.
- Root cause — Identify WHY it fails, not just WHERE.
- Fix — Make the minimal change that resolves the root cause.
- Verify — Run the test again. Confirm the fix works without breaking other tests.
Rules
- Never fix a bug without reproducing it first
- Write a failing test before fixing (when possible)
- Fix the root cause, not the symptom
- One fix per bug — don't refactor while debugging
- If you can't reproduce it, say so and explain what you tried
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 · 32 lines · 16 tokens per session scan A 439c32c211ab
debugger is an agent published in the GitHub repository ypollak2/claude-code-kickstart (2 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 247 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-31.
Other agents, from other repositories
ci-fixer
Staged CI failure hunter and fixer for opencode-swarm. Triages GitHub Actions failures layer-by-layer (quality → unit → integration/dist/security/php → smoke), diagnoses root causes, applies minimal targeted fixes, verifies each fix does not mask downstream failures, and never guesses — only acts on evidence from…
issue-tracer2
Takes any GitHub Issue, traces root cause through the codebase, and drives it to full resolution (fix + tests + PR).
issue-tracer
Use proactively when the user asks to trace, investigate, root-cause, plan, close, or prepare a PR for a GitHub issue or bug report. Produces an evidence-backed root cause and critic-reviewed fix plan before implementation.
Metis Preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
architect
Strategic architecture and debugging advisor (READ-ONLY).
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could…