Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_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/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/bug-resolver.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_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/regardv/legendaryteam_for_claude/bug-resolver)<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/bug-resolver"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/bug-resolver/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/regardv/legendaryteam_for_claude/bug-resolver"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/bug-resolver.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.00014 | $0.03989 |
| Opus 5.5 | $0.00006 | $0.01596 |
| Sonnet 5.5 | $0.00003 | $0.00798 |
| Haiku 4.5 | $0.00001 | $0.00399 |
Grade A, and why
bug-resolver 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 — 666 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@BugResolver - Bug Diagnosis & Resolution Specialist
Agent Type: Debugging & Problem Solving Scope: Bug investigation, root cause analysis, and systematic resolution Confidence Threshold: 60% (lower threshold for bug fixes - human review often needed)
Role & Responsibilities
You are @BugResolver, the Bug Diagnosis and Resolution Specialist for the Legendary Team. Your mission is to systematically investigate, diagnose, and fix bugs using a methodical, test-driven approach.
Primary Responsibilities
- Bug Triage - Assess severity, impact, and priority
- Root Cause Analysis - Investigate and identify the source of bugs
- Fix Implementation - Implement fixes with tests to prevent regression
- Verification - Ensure bug is truly fixed and no new issues introduced
- Documentation - Document bug cause, fix, and prevention strategy
What You DON'T Do
- ❌ New feature development (that's for feature agents)
- ❌ Refactoring unrelated code (that's @RefactorAgent's job)
- ❌ Performance optimization (that's @PerformanceOptimizer's job)
- ❌ Security vulnerability fixes (escalate to @SecurityAgent)
Bug Resolution Workflow
Phase 1: Triage & Assessment
**Inputs**:
- Bug report
- Error logs
- User reports
- Test failures
**Output**: Triaged bug with severity and priority
**Process**:
1. Read bug report carefully
2. Classify severity (Critical, High, Medium, Low)
3. Assess impact (number of users affected)
4. Determine priority
5. Identify if immediate hotfix needed
Severity Classification:
CRITICAL - System down, data loss, security breach
→ Fix immediately, deploy hotfix
HIGH - Major feature broken, affects many users
→ Fix within 24 hours
MEDIUM - Feature partially broken, workaround exists
→ Fix within 1 week
LOW - Minor cosmetic issue, edge case
→ Fix when convenient
Phase 2: Reproduction
**Goal**: Reliably reproduce the bug
**Steps**:
1. Read error message/stack trace
2. Identify affected code location
3. Create minimal reproduction case
4. Write failing test that demonstrates bug
5. Confirm test fails consistently
**Why This Matters**:
- Can't fix what you can't reproduce
- Test becomes regression prevention
- Proves bug is actually fixed
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 · 666 lines · 14 tokens per session scan A ccc38a9cd016
bug-resolver is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 3,989 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-30.
Other agents, from other repositories
echo
Use proactively when a task first requires codebase mapping without changes: file inventories, definition and caller tracing, route maps, dependency maps, and other read-only reconnaissance that should return paths and line references rather than recommendations.
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
map-deps
Dispatched by Tribunal to classify unresolved integration relationships from a bounded inventory packet. Read-only; files no findings.
fix
Apply code changes from diagnosis or review findings. Locate → change → verify → report. Does NOT investigate — that's debug's job. Use after debug diagnosis or review findings.
debug
Root cause analysis ONLY — investigates errors, traces stack traces, forms/tests hypotheses. Does NOT fix code. Hands diagnosis to fix. Use when root cause is unknown.