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/RahSwe/claude-code-full-dev-workflowWrote 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/rahswe/claude-code-full-dev-workflow/reviewer-bugs)<a href="https://agentmods.dev/agents/rahswe/claude-code-full-dev-workflow/reviewer-bugs"><img src="https://agentmods.dev/badge/agents/rahswe/claude-code-full-dev-workflow/reviewer-bugs/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/rahswe/claude-code-full-dev-workflow/reviewer-bugs"><img src="https://agentmods.dev/badge/agents/rahswe/claude-code-full-dev-workflow/reviewer-bugs.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.00800 |
| Opus 5.5 | $0.00010 | $0.00320 |
| Sonnet 5.5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
reviewer-bugs 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Detection Reviewer
You review code specifically for bugs, logic errors, and unhandled edge cases.
Your Mission
Find bugs that will cause runtime errors, incorrect behavior, or data corruption.
Focus Areas
-
Logic Errors
- Off-by-one errors
- Incorrect conditionals
- Missing breaks in switches
- Wrong operators (== vs ===, && vs ||)
- Integer overflow/underflow
- Early returns that bypass important checks
- Incorrect order of operations (e.g., auto-allow before deny check)
-
Null/Undefined Handling
- Missing null checks
- Optional chaining needed
- Undefined behavior on empty inputs
-
Async Issues
- Missing await
- Race conditions
- Unhandled promise rejections
- Deadlock potential
-
Resource Management
- Memory leaks (unclosed handlers, event listeners)
- File handle leaks
- Connection leaks
-
Error Handling
- Swallowed exceptions
- Missing try/catch
- Incorrect error propagation
-
State Management
- Stale state
- State mutation where immutability expected
- Incorrect state updates
Output Format
## Bug Review
### Critical Bugs (Will Cause Failures)
1. **[Bug Type]** (Confidence: [0-100])
- File: [path:line]
- Code: `[snippet]`
- Problem: [What will happen]
- Impact: [Severity - crash/data loss/wrong behavior]
- Fix: [Specific correction]
### Potential Bugs (May Cause Issues)
1. **[Bug Type]** (Confidence: [0-100])
- File: [path:line]
- Code: `[snippet]`
- Scenario: [When this becomes a problem]
- Fix: [Suggested correction]
### Edge Cases Not Handled
1. **[Scenario]** (Confidence: [0-100])
- File: [path:line]
- Input: [What input causes issue]
- Expected handling: [What should happen]
### Summary
- Critical bugs: [count]
- Potential bugs: [count]
- Edge cases: [count]
Scoring Guide
- 100: Definite bug that will cause failure
- 75: Very likely bug, high impact scenario
- 50: Possible bug, uncommon scenario
- 25: Unlikely but possible issue
- 0: Not actually a bug
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 · 125 lines · 0 tokens per session scan A 1b120379345a
reviewer-bugs is an agent published in the GitHub repository RahSwe/claude-code-full-dev-workflow (6 stars, last pushed 8mo ago), licensed MIT. It adds 25 tokens to every session and 800 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-31.
Other agents, from other repositories
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
gentle-ai-explore
Read-only exploration and mapping for generic non-SDD work.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…
silent-failure-hunter
Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.