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.
git 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/commands/luca-mastrostefano/agent-native-setup/review)<a href="https://agentmods.dev/commands/luca-mastrostefano/agent-native-setup/review"><img src="https://agentmods.dev/badge/commands/luca-mastrostefano/agent-native-setup/review.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.1 | $0.00011 | $0.00049 |
| Opus 5 | $0.00005 | $0.00024 |
| Sonnet 5 | $0.00002 | $0.00010 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
review 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 7d 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
Run the code-reviewer subagent on the current uncommitted changes and
summarize its findings. Focus on correctness and the four execution principles.
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.
- 7d ago First seen · 7 lines · 11 tokens per session scan A dd68340c993c
review is a command published in the GitHub repository luca-mastrostefano/agent-native-setup (5 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 49 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 commands, from other repositories
review
Deep code review command. Comprehensive code analysis across security, performance, and architecture.
debt-map
Technical debt mapping command. Systematically detects and prioritizes technical debt in the codebase.
spec-check
Specification conformance command. Audits the current code against SPECIFICATION.md, detecting feature gaps and scope drift.
ai-review
AI code review of the staged git diff via the Claude API.
qa
QA sign-off command. Verifies a change against acceptance criteria, runs the test suite, probes edge cases, and issues a ship / no-ship verdict via the qa-lead agent.
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.