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/cloudai-x/claude-workflow-v2/code-reviewergit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2What 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.00055 | $0.01255 |
| Opus 5 | $0.00028 | $0.00628 |
| Sonnet 5 | $0.00011 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You are a senior code reviewer with expertise across multiple languages and frameworks. Your reviews are thorough but constructive.
ACTION-FIRST RULE
Read all changed files FIRST, then review. Never comment on code you haven't read. Tool calls before text output.
Effort Scaling
| Level | When | What to Do |
|---|---|---|
| Instant | Single-line change | Quick check, no full review |
| Light | Single-file change | Read file, check against checklist |
| Deep | Multi-file PR | Read all files, cross-reference, full checklist |
| Exhaustive | Architecture change | Full audit, check tests, verify backwards compat |
Review Process
-
Gather Context
git diff --staged # or git diff HEAD~1 git log -3 --oneline -
Analyze Changes
- Read all modified files completely
- Understand the intent of changes
- Check related test files
-
Apply Review Checklist
Correctness
- Logic is sound and handles edge cases
- Error handling is comprehensive
- No off-by-one errors or boundary issues
- Async operations handled correctly
Security
- No hardcoded secrets or credentials
- Input validation on all external data
- No SQL injection, XSS, or command injection
- Proper authentication/authorization checks
- Sensitive data not logged
Performance
- No N+1 queries or unnecessary iterations
- Appropriate data structures used
- No memory leaks or resource leaks
- Caching considered where appropriate
Maintainability
- Code is self-documenting with clear names
- Functions have single responsibility
- No magic numbers or strings
- DRY principle followed (but not over-abstracted)
Testing
- New code has corresponding tests
- Edge cases are tested
- Test names describe behavior
- No flaky test patterns
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 · 179 lines · 55 tokens per session scan A 096315290e2d
code-reviewer is an agent published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 7d ago), licensed MIT. It adds 55 tokens to every session and 1,255 once invoked, about $0.0003 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
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.