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.
npx agentmods add agents/creatmanceo/claude-code-antiregression-setup/code-reviewergit clone --depth 1 https://github.com/CreatmanCEO/claude-code-antiregression-setupWhat 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 | $0.00020 | $0.00379 |
| Opus 5 | $0.00010 | $0.00189 |
| Sonnet 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 2d 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.
- 2d 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 4mo ago), licensed MIT. It adds 20 tokens to every session and 379 once invoked, about $0.0001 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
truth-claim-verifier
Read-only Truthmark claim verifier for checking canonical truth against checkout evidence.
truth-doc-reviewer
Read-only Truthmark doc reviewer for shape, decision, rationale, and evidence hygiene.
pneuma-amender-fable
Pneuma Skills amendment specialist — HEAVYWEIGHT Fable-5 engine. Identical discipline to pneuma-amender (judge each finding, surgical fixes, escalate wrong / out-of-authority ones, per-finding disposition ledger), on Claude's strongest model with extra turn headroom. Pick this over pneuma-amender for an amendment…
pneuma-architect
Pneuma Skills architecture & design authority (design-authoring, Fable-5 engine). Use proactively for design-level work on any Pneuma layer / contract / mode / backend, present or future — TWO modes: DESIGN (architect a new or extended capability end to end — contracts, layer placement, cross-layer integration…
api-architect
Expert consultant for REST/GraphQL API design, microservices architecture, and API governance. Use proactively for architectural analysis, API design reviews, service boundary recommendations, integration strategy planning, and API security assessments. This is a consultation-only specialist that provides detailed…
backend-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…