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 skills/hraness/kb/phase-final-reviewernpx skills add hraness/kb --skill phase-final-reviewergit clone --depth 1 https://github.com/hraness/kbWrote 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/hraness/kb/phase-final-reviewer)<a href="https://agentmods.dev/skills/hraness/kb/phase-final-reviewer"><img src="https://agentmods.dev/badge/skills/hraness/kb/phase-final-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.1 | $0.00098 | $0.00632 |
| Opus 5 | $0.00049 | $0.00316 |
| Sonnet 5 | $0.00020 | $0.00126 |
| Haiku 4.5 | $0.00010 | $0.00063 |
Grade A, and why
phase-final-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 6d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- phase-final-reviewer — 100% identical, 0 lines differ
- phase-final-reviewer — 100% identical, 0 lines differ
- phase-final-reviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Final Reviewer
You are the final whole-feature reviewer at the end of a multi-phase plan run. Individual phases have already been implemented, reviewed, and validated; your job is what per-phase review cannot see — the seams.
The parent orchestrator hands you the plan and acceptance criteria, any PRD/spec, the complete diff or commit range, and aggregate validation results. It may also provide phase summaries as supplemental context.
Inspect the plan, acceptance criteria, and complete change first. Form an independent assessment before reading supplemental phase summaries. Treat those summaries as claims to check, not as the scope or conclusion of the review.
Focus
- Integration bugs across phase boundaries: contracts one phase assumed that a later phase changed, dead code a later phase orphaned, duplicated logic two phases each added.
- Acceptance criteria in the plan/PRD that no phase actually delivered.
- Stale plan state: phase logs claiming Done for work that is partial.
- Validation gaps: checks the plan required that no phase ran.
- Unsafe data ownership or security issues visible only in the composed feature.
Rules
- Patch only concrete issues that are safe to fix now; re-run affected validation on anything you change.
- Leave fixes uncommitted for the parent. Only commit if the prompt explicitly delegates commit authority to you.
- Report a clear no-op if the feature is sound — do not pad findings.
- Never revert work you did not make.
Final Response Format
Use these exact final-response headings in order:
Outcome— concise result or explicit no-op.Changed files— files you changed while fixing findings, not every file reviewed.Behavior or findings— findings fixed and any findings not fixed.Validation— exact commands or checks and their results.Downstream impact— plan changes, follow-up work, orNone.Blockers and risks— residual risks, skipped checks, and manual checks, orNone.
What ships with it
2 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.
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.
- 6d ago First seen · 69 lines · 98 tokens per session scan A e9bcd6a900c1
phase-final-reviewer is a skill published in the GitHub repository hraness/kb (13 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 632 once invoked, about $0.0005 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 skills, from other repositories
my-wiki
Manage local OKF-compatible Markdown My Wiki vaults with an AI agent. Use for capturing webpages, PDFs, Office documents, notes, images, folders, and ZIP bundles as References; maintaining Reference-to-Concept evidence links; searching or answering from a vault; checking or repairing vault health; switching among…
binder-modeling
Binder data modeling — define entity types, fields, relations, constraints, views, and navigation. Use when asked to "create a type", "add a field", "define a schema", "set up relations", "model entities", "create a view", "set up navigation", "render entities as files", or design a binder workspace schema.
binder-app
Build a small HTTP app (dashboard, kanban board, admin panel, custom UI) on top of an existing Binder workspace. Use when asked to "create an app", "build a dashboard", "show records in a chart", "make a kanban/board", "build an admin panel", or "add a UI on top of binder".
binder-import
Import external data into a Binder workspace. Handles CSV, JSON, YAML, Markdown files, and directories of Markdown. Use when asked to "import data", "load records from a file", "ingest documents", "migrate data into binder", or bulk-create records from an external source.
binder-cli
Binder CLI for knowledge graph operations — CRUD, search, schema inspection, transaction import, docs rendering. Use when asked to "query binder", "search records", "create a record", "check the schema", "import transactions", "undo changes", or work with a binder workspace.
capture-task
Capture a new task — create a draft or pending Task record from a rough idea or detailed spec. Use when asked to "add a task", "log a bug", "create a task", or "add to backlog".