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 jwilger/ai-plugins --skill final-reviewgit clone --depth 1 https://github.com/jwilger/ai-pluginsWrote 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/jwilger/ai-plugins/final-review)<a href="https://agentmods.dev/skills/jwilger/ai-plugins/final-review"><img src="https://agentmods.dev/badge/skills/jwilger/ai-plugins/final-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/jwilger/ai-plugins/final-review"><img src="https://agentmods.dev/badge/skills/jwilger/ai-plugins/final-review.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.08447 |
| Opus 5.5 | $0.00022 | $0.03379 |
| Sonnet 5.5 | $0.00011 | $0.01689 |
| Haiku 4.5 | $0.00005 | $0.00845 |
Grade A, and why
final-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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
7 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.
- .plugin-eval/benchmark.json 5.0 KB
- .plugin-eval/workspace/final-review-status-contract.mjs 3.3 KB runs code
- .plugin-eval/workspace/README.md 374 B
- .plugin-eval/workspace/verify-final-review-status.mjs 835 B runs code
- .plugin-eval/workspace/verify-final-review-status.test.mjs 2.9 KB runs code
- references/mcp-protocol.md 44 KB
- references/proportional-review-policy.md 9.3 KB
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 Changed · -18 lines 7bf3e8e79ba9
- 12d ago Changed · -114 lines e24d05ff01fc
- 14d ago Changed · +80 lines 95265b909acd
- 19d ago Changed a7655d9ef152
- 21d ago Changed · -2 lines 323dc4a2c95f
- 25d ago Changed · -22 lines 4400695edfd6
- 1mo ago Changed fdd062730754
- 1mo ago Changed · +16 lines 6c93c1c0cd31
- 1mo ago First seen · 660 lines · 54 tokens per session scan A ff5a9a10ca4d
final-review is a skill published in the GitHub repository jwilger/ai-plugins (3 stars, last pushed 3d ago), with no licence file. It adds 54 tokens to every session and 8,447 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-08-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…