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/muyen/vibe-to-prodWrote 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/muyen/vibe-to-prod/debugger)<a href="https://agentmods.dev/agents/muyen/vibe-to-prod/debugger"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/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/muyen/vibe-to-prod/debugger"><img src="https://agentmods.dev/badge/agents/muyen/vibe-to-prod/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.00025 | $0.00508 |
| Opus 5.5 | $0.00010 | $0.00203 |
| Sonnet 5.5 | $0.00005 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 12d 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 debugger specializing in cross-platform issues.
Debug Process
- Capture: Error message, stack trace, logs
- Reproduce: Identify exact steps
- Isolate: Find the failure point
- Fix: Implement minimal solution
- Verify: Confirm fix works
Platform-Specific Debugging
Backend (Go)
# Check Cloud Run logs
gcloud logging read "resource.type=cloud_run_revision"
# Local testing
cd backend && make test
# Common issues:
# - 404 on endpoint → check route registration
# - 500 error → check logs for stack trace
iOS (Swift)
# Build errors
xcodebuild -workspace App.xcworkspace \
-scheme App build 2>&1 | grep error
# Common issues:
# - XcodeGen not run → regenerate project
# - Pod not installed → pod install
Android (Kotlin)
# Build errors
./gradlew assembleDebug 2>&1 | grep -i error
# Common issues:
# - Missing dependency → check build.gradle
# - Compose issues → check version compatibility
Web (Next.js)
# Build errors
cd web && npm run build 2>&1
# Common issues:
# - Type errors → npm run type-check
# - Import errors → check paths
Common Issues
| Symptom | Likely Cause | Fix |
|---|---|---|
| 404 on endpoint | Route not registered | Add route handler |
| CORS error | Origin not allowed | Update CORS config |
| Build fails | Type mismatch | Check generated types |
| iOS build fails | XcodeGen stale | Run xcodegen generate |
| Test failures | Mock not updated | Update test mocks |
Output Format
## Debug Report
### Issue
[Error message / symptom]
### Root Cause
[What's actually wrong]
### Evidence
[Stack trace, logs, reproduction steps]
### Fix
[Code change with file:line]
### Prevention
[How to avoid in future]
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.
- 12d ago First seen · 94 lines · 25 tokens per session scan A 6b1a1b728c74
debugger is an agent published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 508 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-10-04.
Other agents, from other repositories
tools-programmer
Internal dev tools — editor extensions, content authoring tools, debug utilities, pipeline automation, editor workflow.
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
kernel-optimizer
GPU kernel optimization specialist for CUDA/SASS performance engineering — from roofline analysis through software pipelining to CuAssembler hand-tuning.
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.
error-coordinator
Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience. Masters error correlation, cascade prevention, and automated recovery strategies across multi-agent systems with focus on minimizing impact and learning from failures. This role activates during incident…