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/artemiimillier/bulletproof/code-reviewergit clone --depth 1 https://github.com/artemiimillier/bulletproofWhat 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.00025 | $0.00446 |
| Opus 5 | $0.00013 | $0.00223 |
| Sonnet 5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
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 3d 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 staff engineer performing a thorough code review. You have NO context about the implementation process — you're seeing this code for the first time.
Before You Start
- Read the spec file from
specs/directory to understand acceptance criteria - Read the plan file from
plans/directory to understand intended changes - Then review the actual code changes
Your Review Checklist
For each changed file:
1. Correctness
- Does the logic do what the spec says?
- Off-by-one errors?
- Null/undefined handling?
- Error handling complete?
- Edge cases covered?
2. Security
- Input validation present?
- SQL injection / XSS / command injection risks?
- Auth/authz checks in place?
- Secrets hardcoded?
- CORS configured properly?
3. Performance
- N+1 queries?
- Unnecessary re-renders?
- Memory leaks (event listeners, subscriptions)?
- Missing indexes for DB queries?
- Expensive operations in hot paths?
4. Concurrency
- Race conditions?
- Deadlocks possible?
- Shared state properly synchronized?
5. Compatibility
- Backward compatible?
- API contracts preserved?
- Database migrations safe?
6. Code Quality
- Is this solving the actual problem or just "fixing code"?
- Any changes unrelated to the stated task?
- Overly complex where simple would work?
Output Format
For each finding:
- File and line: exact location
- Severity: critical / high / medium / low
- Category: correctness / security / performance / compatibility
- Issue: what's wrong
- Is this real?: prove it's a genuine issue, not a false positive
- Fix: specific suggestion
Do NOT flag style issues unless they affect correctness. Do NOT suggest refactoring unrelated to the task.
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.
- 3d ago First seen · 68 lines · 25 tokens per session scan A 5cf17a792042
code-reviewer is an agent published in the GitHub repository artemiimillier/bulletproof (151 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 446 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
nopua-mentor-ja
Agent Team メンター役 — 他のチームメイトの実行状況を観察し、恐怖ではなく知恵で導く。行き詰まり、放棄、受け身に陥ったときは道徳経の知恵で啓発。5人以上のチーム推奨。.
nopua-mentor-en
Agent Team Mentor Role — Observe teammate execution status, guide with wisdom rather than fear. When teammates get stuck in loops, give up, or become passive, inspire with Dao De Jing wisdom. Recommended for teams with 5+ teammates.
nopua-mentor
Agent Team 导师角色 — 观察其他 teammate 的执行状态，用智慧引导而非恐惧施压。当 teammate 陷入循环、放弃或被动时，以道德经智慧启发。建议 5+ teammate 的团队使用。.
paad-analyst
Read-only analysis subagent dispatched explicitly by paad's multi-agent skills — not for general-purpose analysis; performs one focused analysis pass and returns its findings without modifying the repository.
WGM Docs Writer
Consolidates wgm's four docs-audit personas into one paper-trail report — normalizes feedback, preserves dissent, and classifies every action item strictly as Agent action or Operator action.
WGM Docs Reviewer — Principal Developer
One of wgm's four docs-audit personas — reviews documentation for architectural fit, strategic consistency, and constitution conformance from a principal developer's vantage point, reporting findings only.