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 r13v/pi-feature-dev --skill final-checkgit clone --depth 1 https://github.com/r13v/pi-feature-devWrote 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/r13v/pi-feature-dev/final-check)<a href="https://agentmods.dev/skills/r13v/pi-feature-dev/final-check"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/final-check/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/r13v/pi-feature-dev/final-check"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/final-check.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.00023 | $0.00271 |
| Opus 5.5 | $0.00009 | $0.00108 |
| Sonnet 5.5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
final-check 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 today.
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
Final Check
What else have we missed? Compare the requested outcome with the current work and validation evidence. Inspect only the affected scope and dependencies needed to resolve a concrete concern; do not start an unrelated repository audit.
When the work renames or removes a public name, such as a function, a command, a flag, or a domain term, search the whole repository, including the documentation and the site pages, for the old name.
Fix confirmed in-scope gaps when implementation is already authorized. If the request is review-only, report findings without editing. Reuse passing checks; rerun or broaden them only after changes, failures, or a newly identified risk.
Finish when acceptance criteria are supported and no known in-scope blocker
remains. Report material findings, fixes, checks actually run, and unverified
requirements. When the repository already keeps docs/backlog/ items or the
user asks, give real gaps outside the scope to the add mode of the backlog
skill. When ship runs this check, list those gaps separately for ship
instead. If nothing further is needed, say so without inventing work.
What ships with it
1 file 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.
- today Changed · +4 lines 4ecd447a1400
- 9d ago Changed 4612564b648f
- 18d ago Changed · +1 lines f322b6fb8445
- 1mo ago Changed · +2 lines 3d66c6d15d0e
- 1mo ago Changed · +12 lines · -5 tokens per session be40291ff840
- 2mo ago First seen · 7 lines · 28 tokens per session scan A 6d2e110a8684
final-check is a skill published in the GitHub repository r13v/pi-feature-dev (3 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 271 once invoked, about $0.0001 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…