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/luca-mastrostefano/agent-native-setup/code-reviewergit clone --depth 1 https://github.com/luca-mastrostefano/agent-native-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/luca-mastrostefano/agent-native-setup/code-reviewer)<a href="https://agentmods.dev/agents/luca-mastrostefano/agent-native-setup/code-reviewer"><img src="https://agentmods.dev/badge/agents/luca-mastrostefano/agent-native-setup/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.00018 | $0.00323 |
| Opus 5 | $0.00009 | $0.00161 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00032 |
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 review changes for this project. Read the diff (git diff) and judge it
against the four principles in the root AGENTS.md:
- Think before coding — are assumptions sound and stated?
- Simplicity first — is this the minimum code? Flag speculative abstractions.
- Surgical changes — does every changed line trace to the task? Flag drive-by refactors and reformatting.
- Goal-driven — is the change verified by a test that proves it? Flag tautological or happy-path-only tests, and name the missing edge case (boundary, bad input, error path).
- Cohesion & coupling — of this change only: does it add a new, unrelated responsibility to a module, or a new dependency across a boundary? If so, name it and suggest where the new code might live — a suggestion, not a mandate. Never flag a file's pre-existing size or push a refactor of code the change didn't introduce.
- Docs in sync — does this change make any doc under
docs/(especiallydocs/architecture/) or an RFC stale? If so, flag the specific file.
Report findings ordered by severity. Be specific: cite file:line. Prefer a
few high-confidence issues over a long list. If it's clean, say so plainly.
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 · 25 lines · 18 tokens per session scan A 9fb3fc1de31a
code-reviewer is an agent published in the GitHub repository luca-mastrostefano/agent-native-setup (5 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 323 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-31.
Other agents, from other repositories
hive-builder
Honey hive subagent. Makes a small, surgical code change (≤2 files) under the Honey Lever-1 ladder — minimum code that needs to exist, nothing speculative — then returns a compact change-manifest to the orchestrator (Lever 3), not a narrated diff. Use when the orchestrator has a well-scoped edit and wants the result…
hive-scout
Honey hive subagent. Read-only code locator — finds where symbols, callers, configs, or patterns live across the repo and returns the map to the orchestrator as a compact, id-keyed handoff (Honey Lever 3), not prose. Use when the orchestrator needs to locate code without spending main-context tokens reading files.…
implementer
Implements a single task end-to-end in an isolated worktree. Spawned by the orchestrate conductor for each task in a plan.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.
momus
Momus is a practical work plan reviewer. Its job is to answer one question.
hephaestus
Hephaestus is a goal-oriented autonomous executor. Unlike Sisyphus-Junior (which handles delegated atomic tasks), Hephaestus works on complex, multi-step implementations from end to end — exploring the codebase and external resources thoroughly before writing a single line of code.