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 skills add ai-driven-dev/framework --skill 05-reviewgit clone --depth 1 https://github.com/ai-driven-dev/frameworkWrote 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/skills/ai-driven-dev/framework/05-review)<a href="https://agentmods.dev/skills/ai-driven-dev/framework/05-review"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/05-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ai-driven-dev/framework/05-review"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/05-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00054 | $0.00275 |
| Opus 5.5 | $0.00022 | $0.00110 |
| Sonnet 5.5 | $0.00011 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
05-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 5d 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
Review
flowchart LR
all([all axes]) --> prepare
one([one axis named]) --> prepare
prepare --> review-code & review-functional & review-relevancy --> finalize
finalize --> approve([approve])
finalize --> changes([changes-requested])
finalize --> blocked([blocked])
changes -.->|a later run| all
blocked -.->|a later run| all
Actions
Run the flow above, reading only the next action file.
| Action | Does |
|---|---|
| prepare | resolve the diff and open the round |
| review-code | grade the changed lines on clean code |
| review-functional | trace the diff against the plan's criteria |
| review-relevancy | judge whether the change belongs |
| finalize | judge the round and check its shape |
Transversal rules
- Ask which entry the caller wants when the request does not say.
- Review statically: never run the app.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- actions/01-prepare.md 783 B
- actions/02-review-code.md 704 B
- actions/03-review-functional.md 1.9 KB
- actions/04-review-relevancy.md 813 B
- actions/05-finalize.md 606 B
- assets/review-template.md 1.0 KB
- assets/review-validator.yml 459 B
- references/report-contract.md 1.1 KB
- references/review-rubric.md 845 B
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.
- 5d ago Changed · -4 lines · +10 tokens per session 85cc0fba4d30
- 1mo ago First seen · 41 lines · 44 tokens per session scan A 9a81cfc17d5a
05-review is a skill published in the GitHub repository ai-driven-dev/framework (524 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 275 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
github
Manage the full GitHub workflow from the terminal — auth, issues, pull request lifecycle (branch/commit/open/CI/merge), code review, and repo management. Uses the gh CLI when present, with a git + REST API fallback. Use when asked to "open a PR", "create an issue", "review this PR", "check CI", "list issues".
pr-gates
This skill should be used when the user asks to "open a PR", "prepare for review", "address review comments", "run gates", or "verify before pushing" in this repository. Enforces preflight/gate workflow, migration safety, and review-evidence closure.
Codex
Guides operator-owned delegation to Codex when the task fits a bounded coding lane, review pass, or worktree-isolated implementation track.
GitHub PR Workflow
Move cleanly through branch, diff, review, validation, and PR update steps without losing scope or repository-native workflow.
gh-pr
Create, review, or manage GitHub pull requests. Use when asked to open, check, or merge a PR.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.