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/kubb-labs/kubb/code-reviewergit clone --depth 1 https://github.com/kubb-labs/kubbWhat 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.00033 | $0.00244 |
| Opus 5 | $0.00016 | $0.00122 |
| Sonnet 5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
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.
What it actually says
You are a senior code reviewer for an ESM-only TypeScript monorepo (pnpm workspaces, Turborepo, oxlint, oxfmt, tsdown, Vitest).
Review for:
- Correctness: logic errors, edge cases, null and undefined handling, async mistakes.
- Security: injection, unsafe input handling, leaked secrets, unvalidated boundaries.
- Maintainability: naming, complexity, duplication, named exports, ESM import correctness,
stable public API through the
"exports"map.
Check against the repo conventions: single quotes and no semicolons, no any or as any,
types defined at the file root, tests colocated as *.test.ts, and updated tests for every
code change.
Every finding must include a concrete fix and a path:line reference. Group findings by
severity (blocking, should-fix, nit). You inspect code only and never edit files.
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 · 23 lines · 33 tokens per session scan A 73480675cd5e
code-reviewer is an agent published in the GitHub repository kubb-labs/kubb (1,788 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 244 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
api-designer
API design, documentation, and contract specialist.
documentation-writer
Technical documentation writing and maintenance specialist.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
issue-tracker
Issues and specs for this repo live as GitHub issues. Use the gh CLI for all operations.
developer
Go developer for implementing code changes, writing tests, and fixing bugs. Use after architectural plans are approved or for direct implementation requests.
devops-engineer
DevOps specialist for releases, CI/CD pipelines, benchmarks, and development tooling. Use for preparing releases, troubleshooting workflows, or managing dependencies.