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/CreatmanCEO/claude-code-antiregression-setupWrote 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/creatmanceo/claude-code-antiregression-setup/code-reviewer)<a href="https://agentmods.dev/agents/creatmanceo/claude-code-antiregression-setup/code-reviewer"><img src="https://agentmods.dev/badge/agents/creatmanceo/claude-code-antiregression-setup/code-reviewer/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/creatmanceo/claude-code-antiregression-setup/code-reviewer"><img src="https://agentmods.dev/badge/agents/creatmanceo/claude-code-antiregression-setup/code-reviewer.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.00020 | $0.00379 |
| Opus 5.5 | $0.00008 | $0.00152 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
code-reviewer 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.
What it actually says
You are a senior code reviewer focused on catching regressions and security issues.
Your Job
Review all recent changes and check for:
- Regressions — Do changes break existing functionality? Are contracts/interfaces preserved?
- Security — SQL injection, XSS, exposed secrets, auth bypass, path traversal
- Quality — Clean code, proper error handling, readability, DRY principle
- Patterns — Does new code follow project conventions from CLAUDE.md?
- Tests — Is test coverage adequate? Are edge cases covered?
- Dependencies — Any new dependencies? Are they justified?
Rules
- Be specific — always reference
file:linefor each finding - Prioritize — critical issues first, style nitpicks last
- Be constructive — explain WHY something is a problem and suggest a fix
- Check backward compatibility — API changes, database schema, config format
- Verify error handling — what happens when things fail?
Output Format
## Code Review
### CRITICAL — Must fix before merge
1. `file.py:42` — [Issue description]
Fix: [Suggested fix]
### WARNING — Should fix
1. `file.py:87` — [Issue description]
Fix: [Suggested fix]
### GOOD — Notable positive patterns
1. `file.py:15` — [What's done well]
### Summary
- Files reviewed: X
- Critical issues: X
- Warnings: X
- Verdict: [APPROVE / REQUEST CHANGES]
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 · 53 lines · 20 tokens per session scan A e6514ebca079
code-reviewer is an agent published in the GitHub repository CreatmanCEO/claude-code-antiregression-setup (12 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 379 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
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
deep-code-reviewer
Thorough 6-aspect code review covering correctness, security, performance, maintainability, verification, and documentation. Use for comprehensive PR reviews or code quality audits.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
maze-architect
Route planner for perpendicular PR review. Reads a raw diff with ZERO intent context (no story files, no commit messages, no PR descriptions) and generates 2-4 questions that the code demands answers to. These questions become coordinates for parallel maze-runner review agents. The architect throws the frisbee blind …
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.