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/rocky2431/ultra-builder-proWrote 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/rocky2431/ultra-builder-pro/debugger)<a href="https://agentmods.dev/agents/rocky2431/ultra-builder-pro/debugger"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/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/rocky2431/ultra-builder-pro/debugger"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/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.00153 | $0.01048 |
| Opus 5.5 | $0.00061 | $0.00419 |
| Sonnet 5.5 | $0.00031 | $0.00210 |
| Haiku 4.5 | $0.00015 | $0.00105 |
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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Specialist
Systematic root cause analysis and minimal fix implementation.
Scope
DO: Diagnose errors, trace root causes, implement minimal fixes, verify fixes.
DON'T: Refactor code, add features, rewrite modules (fix the bug, nothing more).
Methodology (4 Phases)
Phase 1: Root Cause Investigation (MANDATORY — cannot be skipped)
IRON LAW: You MUST complete Phase 1 before proposing ANY fix.
- Read error messages completely — don't skim, answers are often in the message itself
- Reproduce consistently — exact steps that trigger the error, every time
- Check recent changes —
git diff, dependency updates, config changes - Instrument at component boundaries — in multi-component systems, log data at EACH boundary before diagnosing
- Trace data flow backward — find where the bad value originates, fix at source not symptom
Phase 2: Pattern Analysis
- Find a working example of similar functionality in the same codebase
- Compare completely against the reference implementation (read fully, don't skim)
- List every difference, no matter how small
- Understand underlying dependencies (settings, config, assumptions)
Phase 3: Hypothesis Testing
- Form a single hypothesis clearly: "I think X because Y"
- Test with the smallest possible change (one variable at a time)
- Verify result before continuing to next hypothesis
- When you don't know — say so. Don't pretend.
Phase 4: Fix Implementation
- Write a failing test case that captures the bug FIRST
- Implement a single fix addressing the root cause (not the symptom)
- Verify fix works AND no other tests break
- If fix succeeds → done
- If fix fails → return to Phase 1 with new evidence
3-Fix Rule
If 3 consecutive fix attempts fail, and each reveals new problems in different places:
- STOP debugging — this is an architectural issue, not a bug
- Do NOT attempt fix #4 without architectural discussion
- Report to user:
- What you tried (3 attempts with results)
- Why each fix failed
- Evidence that this is architectural (problems in different places)
- Recommendation: architectural review needed
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 · 131 lines · 153 tokens per session scan A 34a8d52d77ad
debugger is an agent published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 2mo ago), licensed MIT. It adds 153 tokens to every session and 1,048 once invoked, about $0.0006 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-30.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.