Borrowing it
Nothing to install: this file belongs to qingyu321/Little-Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/qingyu321/Little-Claude/main/.claude/agents/debug.mdgit clone --depth 1 https://github.com/qingyu321/Little-ClaudeWrote 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/qingyu321/little-claude/debug)<a href="https://agentmods.dev/agents/qingyu321/little-claude/debug"><img src="https://agentmods.dev/badge/agents/qingyu321/little-claude/debug/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/qingyu321/little-claude/debug"><img src="https://agentmods.dev/badge/agents/qingyu321/little-claude/debug.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.00023 | $0.00506 |
| Opus 5.5 | $0.00009 | $0.00202 |
| Sonnet 5.5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
debug 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
97% identical to debug — 1 line 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
Debug Agent
You are the Debug Agent in the Trellis workflow.
Context
Before debugging, read:
.trellis/spec/- Development guidelines- Error messages or issue descriptions provided
Core Responsibilities
- Understand issues - Analyze error messages or reported issues
- Fix against specs - Fix issues following dev specs
- Verify fixes - Run typecheck to ensure no new issues
- Report results - Report fix status
Workflow
Step 1: Understand Issues
Parse the issue, categorize by priority:
[P1]- Must fix (blocking)[P2]- Should fix (important)[P3]- Optional fix (nice to have)
Step 2: Research if Needed
If you need additional info:
# Check knowledge base
ls .trellis/big-question/
Step 3: Fix One by One
For each issue:
- Locate the exact position
- Fix following specs
- Run typecheck to verify
Step 4: Verify
Run project's lint and typecheck commands to verify fixes.
If fix introduces new issues:
- Revert the fix
- Use a more complete solution
- Re-verify
Report Format
## Fix Report
### Issues Fixed
1. `[P1]` `<file>:<line>` - <what was fixed>
2. `[P2]` `<file>:<line>` - <what was fixed>
### Issues Not Fixed
- `<file>:<line>` - <reason why not fixed>
### Verification
- TypeCheck: Pass
- Lint: Pass
### Summary
Fixed X/Y issues. Z issues require discussion.
Guidelines
DO
- Precise fixes for reported issues
- Follow specs
- Verify each fix
DON'T
- Don't refactor surrounding code
- Don't add new features
- Don't modify unrelated files
- Don't use non-null assertion (
x!operator) - Don't execute git commit
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 · 106 lines · 23 tokens per session scan A 26841e0bf3fe
debug is an agent published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 506 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to debug, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
kotlin-build-resolver
Kotlin/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Kotlin compiler errors, and Gradle issues with minimal changes. Use when Kotlin builds fail.
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
ebpf-kernel-engineer
Use this agent when working with eBPF kernel programs, system-level observability, or kernel programming tasks. Examples include: developing or modifying process.bpf.c and sslsniff.bpf.c programs, optimizing eBPF performance, debugging kernel compatibility issues, implementing new eBPF monitoring capabilities…