post-implementation-verification

post-implementation-verification is a skill for Claude Code, Codex from supportersimulator/3-surgeons. It costs 20 tokens per session (799 once invoked), scanned A, original, MIT.

A completion checklist that verifies an implementation before it is called finished. It checks system health, the actual code changes, regressions, and review requirements.

In plain words
What is it for?
Use it before saying a change is done, ready to merge, implemented, or fully tested.
Why use it?
It reduces the risk of declaring work complete when the change introduced a broken configuration, hidden complexity, or an unreviewed problem.

Skill for Claude CodeCodex

Part of the 3-surgeons plugin — 23 skills, 7 commands, 1 agent, 3 hooks, 1 MCP server shipped together

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/supportersimulator/3-surgeons/post-implementation-verification
Any agent
npx skills add supportersimulator/3-surgeons --skill post-implementation-verification
Clone the repo
git clone --depth 1 https://github.com/supportersimulator/3-surgeons

Made for: Claude Code, Codex.

Or install 3-surgeons, the plugin that ships this one along with the rest of its 23 skills, 7 commands, 1 agent, 3 hooks, 1 MCP server.

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 post-implementation-verification

README.md
[![agentmods](https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/post-implementation-verification.svg)](https://agentmods.dev/skills/supportersimulator/3-surgeons/post-implementation-verification)
Your own site
<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/post-implementation-verification"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/post-implementation-verification.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 799 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00020 $0.00799
Opus 5 $0.00010 $0.00400
Sonnet 5 $0.00004 $0.00160
Haiku 4.5 $0.00002 $0.00080

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

Security

Grade A, and why

post-implementation-verification 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 4d 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.

skills/post-implementation-verification/SKILL.md · 93 lines

How it starts

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

Post-Implementation Verification

Purpose

"It works on my machine" is not verification. This gate ensures that completed work is verified across infrastructure health, regression detection, and adversarial review before anyone claims "done."

Auto-Invocation Trigger

Invoke before ANY of these claims:

  • "Done" / "complete" / "finished" / "implemented"
  • "Ready for review" / "ready to merge"
  • "All tests pass" (verify this claim, do not just assert it)
  • "The fix is in" / "bug is resolved"
  • Transitioning from executing-plans to completion

Checklist

You MUST create a TodoWrite task for each step:

  1. Run gains-gate — is infrastructure still healthy after changes? Changes can break things silently (port conflicts, stale locks, broken configs).

  2. Sentinel re-scan on actual changes — scan the diff of what was actually implemented, not the original plan. Implementation often drifts from plan. The sentinel catches complexity introduced during implementation.

    # Get the diff for sentinel input
    git diff --stat HEAD~N  # or appropriate range
    git diff HEAD~N         # full diff for sentinel content
    
  3. If >3 files changed: quick consensus vote — ask all 3 surgeons: "Did we introduce regression?" with the actual diff as context. This catches issues that tests miss.

  4. Verify tests pass — run the actual test suite. Do not claim tests pass without running them. If no tests exist for the changed code, flag this as a gap.

  5. Counter-position: "What did we miss?" — invoke counter-position with the claim "this implementation is complete and correct." Steelman why it is not.

  6. Present verification results — summarize all findings. Only claim completion if all checks pass. If any check fails, fix the issue and re-run verification.

Diff-Based Sentinel Scan

The post-implementation sentinel scan differs from pre-implementation:

Read the full file on GitHub · 93 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. 4d ago First seen · 93 lines · 20 tokens per session scan A 6060e16a3e06

Subscribe to this mod's changes

post-implementation-verification is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 799 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

skill-creator

Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.

zhayujie/CowAgent · 61 tokens

image-generation

Generate or edit images from text prompts. Use when the user asks to create, draw, design, or edit an image, illustration, photo, icon, poster, or any visual content.

zhayujie/CowAgent · 41 tokens

deepcode-self-refer

Answers questions about Deep Code CLI itself — including features, configuration options, slash commands, Skills, MCP integration, permissions, notifications, session persistence, and troubleshooting. Use this when users ask how to configure or use Deep Code, how to set up an MCP server, configure notifications (such…

lessweb/deepcode-cli · 86 tokens

image-generator

Generate or edit images from text and local files, image URLs, or data URLs through image API. Use when the user asks to create an image, generate from one or more reference images, combine styles or elements across references, or edit a marked region while blending the result into the original scene.

lessweb/deepcode-cli · 62 tokens

weibo-poster

微博内容创作 - 140字优化、话题热搜、@提及策略、配图描述、发布时机.

dongsheng123132/u-claw · 32 tokens

excel-helper

Excel 表格助手 - 公式编写、数据透视表、图表可视化、宏自动化、数据清洗.

dongsheng123132/u-claw · 31 tokens