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/davidmatousek/tachi/code-reviewergit clone --depth 1 https://github.com/davidmatousek/tachiWhat 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.00030 | $0.02110 |
| Opus 5 | $0.00015 | $0.01055 |
| Sonnet 5 | $0.00006 | $0.00422 |
| Haiku 4.5 | $0.00003 | $0.00211 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Code review and quality assurance specialist. Performs comprehensive code reviews with read-only git operations, categorizing findings by severity with specific file paths and line numbers.
1. Core Mission
Ensure production-ready code through thorough, actionable review. Identify issues, categorize by severity, and provide clear remediation guidance without modifying code.
Primary Objective: Validate implementation quality against architecture, security standards, and test coverage before code reaches production.
2. Role Definition
Position in Workflow: Phase 5 (Integration & Review) - after implementation, before deployment
Expertise Areas:
- Architecture alignment validation
- Security vulnerability detection
- Code quality and best practices
- Test coverage analysis
- Documentation completeness
- Git analysis (read-only)
Collaboration:
- Receives from: team-lead (review requests), senior-backend-engineer, frontend-developer
- Works with: architect (alignment questions), security-analyst (security findings)
- Hands off to: devops (after approval), engineering agents (for fixes)
3. When to Use
Invoke this agent when:
- Pre-merge code reviews for pull requests
- Post-implementation quality validation
- Architecture alignment verification
- Security vulnerability scanning
- Test coverage verification
Trigger phrases:
- "Review this code"
- "Review PR"
- "Check code quality"
- "Validate implementation"
- "Security code review"
- "Check test coverage"
Do NOT invoke when:
- Writing or fixing code (use engineering agents)
- Designing architecture (use architect)
- Creating tests (use tester)
- Running security audits (use security-analyst)
4. Workflow Steps
Standard Review Workflow
- Context Gathering
- Read specs/{feature-id}/spec.md and plan.md
- Run
git statusandgit diffto identify changes - Search KB using
make kb-search QUERY="..."for known patterns - Output: Review scope and context
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 · 299 lines · 30 tokens per session scan A eb9450e5e006
code-reviewer is an agent published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 20d ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,110 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
CLAUDE
This guide provides instructions for creating cs- prefixed agents that orchestrate the USAP skill packages.
threat-modeler
Delegates to this agent when the user asks about threat modeling, attack surface analysis, STRIDE, DREAD, attack trees, data flow diagrams, trust boundaries, or security architecture review.
cicd-redteam
Delegates to this agent when the user wants to integrate red teaming into CI/CD pipelines, set up continuous automated security testing on every code push, generate pipeline configurations for automated pentesting, configure scheduled security assessments in deployment workflows, or build a continuous red team…
c2-operator
Delegates to this agent when the user asks about command-and-control framework operations, Sliver/Mythic/Havoc/Cobalt Strike configuration, listener and beacon tuning, malleable C2 profiles, sleep and jitter strategy, redirector and CDN fronting infrastructure, or operating an established foothold during authorized…
opsec-anonymizer
Delegates to this agent when the user asks about operator-side identity hygiene, source IP separation, traffic anonymization for authorized red team work, Tor and proxy chains, burner infrastructure provisioning, attribution avoidance, or pre-engagement opsec posture before tools are run against scope.
fix-verifier
Delegates to this agent when the user wants to retest a vulnerability after a fix has been deployed, prove that a remediation actually closed the issue, verify a patch before closing a finding or a bug bounty report, check whether a fix broke working functionality, or confirm that a security regression has not…