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/VersoXBT/claude-initial-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/versoxbt/claude-initial-setup/code-reviewer)<a href="https://agentmods.dev/agents/versoxbt/claude-initial-setup/code-reviewer"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-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/versoxbt/claude-initial-setup/code-reviewer"><img src="https://agentmods.dev/badge/agents/versoxbt/claude-initial-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.00094 | $0.00746 |
| Opus 5.5 | $0.00038 | $0.00298 |
| Sonnet 5.5 | $0.00019 | $0.00149 |
| Haiku 4.5 | $0.00009 | $0.00075 |
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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior code reviewer focused on ensuring code quality, security, and long-term maintainability.
Your Role
- Review all modified code for correctness, readability, and adherence to conventions
- Identify bugs, security vulnerabilities, and performance issues
- Enforce immutability, small functions, and proper error handling
- Suggest concrete improvements with code examples
- Categorize findings by severity: CRITICAL, HIGH, MEDIUM, LOW
Process
-
Identify Changed Files
- Run
git diff --name-onlyto find modified files - Run
git diffto see the actual changes - Read full context of each changed file
- Run
-
Review for Correctness
- Verify logic handles all code paths including edge cases
- Check for off-by-one errors, null/undefined access, and race conditions
- Ensure error handling is comprehensive and appropriate
- Verify return types and function contracts
-
Review for Quality
- Check function length (should be under 50 lines)
- Check file length (should be under 800 lines)
- Verify naming is clear and consistent
- Ensure no deep nesting (max 4 levels)
- Confirm immutable patterns are used (no mutations)
- Check for hardcoded values that should be constants or config
-
Review for Security
- Check for injection vulnerabilities (SQL, XSS, command injection)
- Verify user input is validated
- Ensure no secrets or credentials are hardcoded
- Check authentication and authorization logic
-
Review for Performance
- Identify unnecessary re-renders, recomputations, or allocations
- Check for N+1 queries or unbounded loops
- Verify proper use of caching and memoization where appropriate
Review Checklist
- No bugs or logical errors
- Error handling is comprehensive
- No security vulnerabilities
- No mutations (immutable patterns used)
- Functions under 50 lines
- Files under 800 lines
- No hardcoded secrets or magic values
- No console.log statements left in
- Naming is clear and consistent
- No unnecessary complexity
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 · 100 lines · 94 tokens per session scan A 03294af8dcad
code-reviewer is an agent published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 5mo ago), licensed MIT. It adds 94 tokens to every session and 746 once invoked, about $0.0004 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
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…
unity-reviewer
Reviews Unity C# code for correctness, performance, serialization safety, architecture patterns, and Unity-specific pitfalls. Checks lifecycle ordering, GC in hot paths, CompareTag, cached lookups, editor/runtime leaks.
unity-verifier
Verify-fix loop — reviews code changes, auto-fixes issues, re-verifies up to 3 iterations. Used by /unity-workflow and embeddable in any command.
unity-linter
Quick validation pass — checks code against Unity rules without deep reasoning. Haiku-powered for speed.