final-review

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

A final checkpoint for a completed feature, where the implementation, tests, requirements, and changed files are presented for human approval. A feature unit is a defined piece of product functionality.

In plain words
What is it for?
It helps validate feature requirements, run available compliance checks, summarize implementation and tests, and request final review and approval.
Why use it?
It creates a clear point to check that the work matches its requirements before it is accepted. It also identifies missing requirements or failed checks that still need attention.

Skill for Claude CodeCodex

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/ateles/final-review
Any agent
npx skills add markmhendrickson/ateles --skill final-review
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/ateles

Made for: Claude Code, Codex.

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/ateles/final-review.svg)](https://agentmods.dev/skills/markmhendrickson/ateles/final-review)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/ateles/final-review"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/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 738 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% 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.00738
Opus 5 $0.00005 $0.00369
Sonnet 5 $0.00002 $0.00148
Haiku 4.5 $0.00001 $0.00074

Measured 5d ago against content hash f54fcb0ab35b, 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 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.

Origin

This is a copy

94% identical to final-review — 10 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.

.claude/skills/final-review/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 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 · 95 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. 5d ago First seen · 95 lines · 10 tokens per session scan A f54fcb0ab35b

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

strands-review

Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…

strands-agents/harness-sdk · 125 tokens

docs-writer

Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…

strands-agents/harness-sdk · 74 tokens

pr-create

Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.

strands-agents/harness-sdk · 32 tokens

local-llm-tool

Local LLM execution tool for text generation and chat through Ollama or vLLM endpoints. Use when: running on-prem inference, calling a local GPU model, or summarizing with a self-hosted LLM.

xuiltul/animaworks · 50 tokens

colm

COLM (Conference on Language Modeling) paper formatting — activate when the user wants COLM template setup, migration, or formatting/compilation fixes.

nanoAgentTeam/research-claw · 32 tokens

conference-research

Academic venue paper discovery — activate when you need to find papers accepted at specific conferences or journals (ACL, EMNLP, NeurIPS, ICML, ICLR, MLSys, etc.), analyze venue acceptance preferences, or look up CFP requirements.

nanoAgentTeam/research-claw · 55 tokens