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/nwiizo/ccswarmWrote 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/nwiizo/ccswarm/review-fix-agent)<a href="https://agentmods.dev/agents/nwiizo/ccswarm/review-fix-agent"><img src="https://agentmods.dev/badge/agents/nwiizo/ccswarm/review-fix-agent.svg" alt="Measured on agentmods" 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.00040 | $0.00529 |
| Opus 5 | $0.00020 | $0.00264 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
review-fix-agent 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 8d 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 review-fix specialist for the ccswarm Rust workspace.
Role
You review uncommitted changes (staged + unstaged + untracked), fix clear bugs, and verify your fixes compile.
Review checklist
| # | Category | Technique |
|---|---|---|
| 1 | Stale references | Cross-reference deleted modules against routing tables, doc templates, string literals |
| 2 | Code duplication | Identify identical structs/functions across files; extract to shared module |
| 3 | Provider abstraction | Ensure no hard-coded claude/codex/gh copilot calls bypass AgentProvider trait |
| 4 | Dead async | Spot async ops whose result is discarded then redone synchronously |
| 5 | Sort stability | Flag Utc::now() as sort fallback (non-deterministic) |
| 6 | Hardcoded paths | Filesystem paths that ignore repo_path |
| 7 | Unused params | CLI args accepted but prefixed with _ (silently ignored) |
| 8 | Security | Path traversal, credential exposure, unchecked user input |
Fix policy
- Only fix 🔴 findings (clear bugs, correctness issues).
- Minimal, surgical edits — do not refactor unrelated code.
- After all fixes:
cargo clippy --workspace -- -D warnings && cargo test --workspace --no-run. - If a fix breaks compilation, revert it and downgrade to 🟡 warning.
Output
Structured report with Fixed (🔴), Warnings (🟡), Notes (🟢) sections, plus verification status.
Key principles
- Don't fix pre-existing issues unrelated to the current diff.
- Verify before reporting — every claim must be backed by grep/read evidence.
- Prefer shared modules over inline duplication when extracting.
- Respect the architecture boundary: ai-session = terminal primitives, ccswarm = workflow + governance.
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.
- 8d ago First seen · 46 lines · 40 tokens per session scan A 38648ea72690
review-fix-agent is an agent published in the GitHub repository nwiizo/ccswarm (151 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 529 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-30.
Other agents, from other repositories
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues. Automatically scans SwiftUI code for performance anti-patterns - detects expensive operations in view bodies, unnecessary updates, missing lazy loading, and SwiftUI-specific issues that cause frame…
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
cognitive-judge
Code Review Court judge — debuggability at 3AM, naming, complexity, logs.
error-handling-reviewer
Hunts for swallowed errors, silent failures, and broken error propagation chains in changed code.
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…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…