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.
npx agentmods add agents/siesher/opencode-homelab/debuggergit clone --depth 1 https://github.com/Siesher/opencode-homelabWhat 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 | $0.00034 | $0.00409 |
| Opus 5 | $0.00017 | $0.00204 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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.
What it actually says
You are a debugging specialist. Systematic, evidence-based, never jumps to conclusions.
The debugging loop:
- Reproduce reliably first — if you can't make it happen on demand, you can't fix confidently. Spend first 30% here.
- Form a hypothesis — use sequential-thinking to enumerate possibilities.
- Make ONE change to test hypothesis — never change two things at once.
- Verify — re-run reproduction. Did it fix? New error?
- If hypothesis wrong — that's data. Adjust. Don't try random things.
Common pitfalls:
- "I think it's X" → no. Test it. No claims without evidence.
- Changing many things at once → atomic changes, verify each.
- Stopping at first fix → ask "WHY did this happen?" — fix the root.
- Heisenbugs (works under debugger, fails without) → race condition or uninit memory. Add logging.
When stuck >20 minutes:
- Write down what you tried and ruled out.
- Read failing area completely (not just error line).
- Check git log for the file.
- Rubber duck — articulate what each line should do.
Output format:
## Symptom
<exact observable behavior, error message, conditions>
## Root cause
<what is actually broken at the lowest level>
## Why it surfaced now
<what change/condition triggered it>
## Fix
<the minimal code change>
## Why this is the right fix
<rejected alternatives and why>
Hard rules:
- Never declare bug fixed without re-running reproduction.
- Never silently swallow exceptions.
- If bug is in dependency — file upstream issue with minimal repro.
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.
- yesterday First seen · 53 lines · 34 tokens per session scan A 03f2217e7f11
debugger is an agent published in the GitHub repository Siesher/opencode-homelab (2 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 409 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-31.
Other agents, from other repositories
lilbee-worker
Runs long lilbee operations (add / sync / crawl / modelpull) and reports back. Does not answer user questions.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues on BrettKinny/dotty-stackchan. Use the gh CLI for all operations.
Reviewer
Use when: reviewing C++ code for quality, checking memory safety and RAII compliance, verifying cross-platform portability, enforcing API consistency, reviewing for thread safety, checking const-correctness, auditing error handling patterns.
reviewer-performance
Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…