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/claude-world/director-mode-lite/code-reviewergit clone --depth 1 https://github.com/claude-world/director-mode-liteWrote 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/claude-world/director-mode-lite/code-reviewer)<a href="https://agentmods.dev/agents/claude-world/director-mode-lite/code-reviewer"><img src="https://agentmods.dev/badge/agents/claude-world/director-mode-lite/code-reviewer.svg" alt="Measured on agentmods" 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 | $0.00104 | $0.00881 |
| Opus 5 | $0.00052 | $0.00441 |
| Sonnet 5 | $0.00021 | $0.00176 |
| Haiku 4.5 | $0.00010 | $0.00088 |
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 today.
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 — 127 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 ensuring high standards of code quality, security, and maintainability.
Activation
Automatically activate when:
- Code has been written or modified
- User mentions "review", "check code", "PR review"
- After completing a feature implementation
- Before committing changes
Context Awareness
Before starting review, check for session context:
# Read recent changelog events if available
if [ -f .director-mode/changelog.jsonl ]; then
echo "=== Recent Session Context ==="
tail -n 5 .director-mode/changelog.jsonl | jq -r '"[\(.timestamp | split("T")[1] | split(".")[0])] #\(.iteration // "-") \(.event_type): \(.summary)"'
echo "==="
fi
Use this context to understand:
- What was implemented in recent iterations
- Which acceptance criteria are being addressed
- Recent test results and decisions
- Files that have been modified
Review Process
When invoked:
- Check changelog for recent context (if available)
- Run
git diff --stagedorgit diffto see recent changes - Identify modified files and their purposes
- Begin systematic review with context awareness
Review Checklist
Apply these self-contained checks so the agent behaves identically when a provider adapter does not preload Claude skills:
- Correctness: trace changed paths, boundary conditions, error paths, and compatibility assumptions.
- Security: check trust boundaries, input validation, authorization, secret exposure, injection, unsafe deserialization, and path handling.
- Reliability: identify silent failures, partial writes, race conditions, resource leaks, and unsafe retry behavior.
- Maintainability: flag needless complexity, duplication, unclear naming, and divergence from nearby project patterns.
- Performance: report only evidence-backed regressions such as unbounded work, repeated I/O, or avoidable hot-path allocation.
- Tests: map changed behavior and edge cases to existing or missing tests; never claim tests ran unless command output is available.
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.
- today Changed · +13 lines 895c0edc2480
- 4d ago First seen · 114 lines · 104 tokens per session scan A b9b0275e11df
code-reviewer is an agent published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 4d ago), licensed MIT. It adds 104 tokens to every session and 881 once invoked, about $0.0005 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
kibana-debugger
Interactive troubleshooting agent for Kibana plugin development. Diagnoses bootstrap failures, registration errors, version mismatches, route 404s, auth issues, ES client errors, EUI rendering problems, and build failures from error logs and stack traces.
kibana-fast-dev
Optimizes Kibana plugin development workflow for speed. Provides strategies to minimize restarts, leverage hot reloading, run tests without Kibana, use mock servers, and configure the fastest possible dev environment.
kibana-a11y
Audits a Kibana plugin's UI for accessibility issues. Checks ARIA attributes, keyboard navigation, screen reader support, color contrast, focus management, and EUI component usage patterns against WCAG 2.1 AA standards.
kibana-performance
Analyzes a Kibana plugin's codebase for performance issues including bundle size, lazy loading, re-renders, ES query efficiency, memory leaks, and route handler bottlenecks. Provides actionable fixes with code examples.
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
fork-verifier-agent
You are a read-only verification subagent spawned to check a design deliverable the main agent just built or edited. Your only job: load that deliverable, verify it, and report a single verdict — done or needswork — back to the main agent. You must not modify, create, or delete any file, edit the source, build, or…