final-review

final-review is a skill for Claude Code, Codex, Cursor from markmhendrickson/foundation. It costs 10 tokens per session (711 once invoked), scanned A, a copy of final-review, MIT.

A final review workflow for a completed feature unit. It checks project configuration, validates the feature specification when possible, and presents changed files, tests, and documentation for human approval.

In plain words
What is it for?
Use it after implementation and passing tests to run compliance checks, summarize the completed work, and prepare it for review.
Why use it?
It helps confirm that an implementation meets its requirements before final approval or merging.

Skill for Claude CodeCodexCursor

Install

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.

agentmods
npx agentmods add skills/markmhendrickson/foundation/final-review
Any agent
npx skills add markmhendrickson/foundation --skill final-review
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/foundation

Made for: Claude Code, Codex, Cursor.

Wrote 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.

agentmods badge for final-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/markmhendrickson/foundation/final-review.svg)](https://agentmods.dev/skills/markmhendrickson/foundation/final-review)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/foundation/final-review"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/final-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 711 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00711
Opus 5 $0.00005 $0.00356
Sonnet 5 $0.00002 $0.00142
Haiku 4.5 $0.00001 $0.00071

Measured 3d ago against content hash 1dd915750944, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

This is a copy

95% identical to final-review — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/skills/final-review/SKILL.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Final Review

Present final implementation for review and approval for Feature Unit {{input:feature_id}}.

Follow foundation/development/feature_unit_workflow.md Step 4 (Checkpoint 2 — Final Review). Configuration is read from foundation-config.yaml.

Implements Checkpoint 2 of the Feature Unit creation workflow. Presents the completed implementation for human review and approval.

Trigger

  • Implementation complete
  • Tests passing
  • PR created (if required by config)

Tasks

  1. Load configuration:

    • Read foundation-config.yaml to get feature unit settings
    • Determine directory structure, testing requirements, git workflow
  2. Run spec compliance validation (if available):

    • Execute spec compliance validation script (if repository has one)
    • If compliance check fails: STOP and present compliance report to user
      • List all gaps found
      • Require user to fix gaps, update spec, or explicitly defer requirements before proceeding
      • Re-run compliance check after fixes
    • If compliance check passes or not available, continue to next step
  3. Gather implementation summary:

    • List all files changed
    • List tests added (with pass status)
    • List documentation updated
    • PR link and status (if PR required)
    • Compliance report link (if generated)
  4. Verify completion:

    • All required tests passing (based on config)
    • Coverage meets configured targets
    • PR created with proper format (if required)
    • Spec compliance validation passed (if available)
  5. Present summary:

    • Files changed (count and key files)
    • Tests added/passing
    • Coverage achieved vs target
    • Documentation updated
    • PR link (if applicable)
    • Spec compliance status (if available)
  6. STOP and prompt user:

    • "Implementation complete. PR: [link]" (if applicable)
    • "Please review the implementation"
    • "Approve for merge? (yes/no)"
    • "Any final changes needed? (list or 'none')"
    • "Spec compliance validation: ✅ Pass / ❌ Fail (see report: [link])" (if available)

Read the full file on GitHub · 94 lines

Changes

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.

  1. 3d ago First seen · 94 lines · 10 tokens per session scan A 1dd915750944

Subscribe to this mod's changes

final-review is a skill published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 711 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to final-review, differing in 7 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens