A final verification workflow for a completed software feature. It first runs tests and checks that documented scenarios are covered, then records the feature’s important decisions and lessons in the project wiki.

Use it to run the full test suite, inspect scenario coverage, report failures or skipped tests, and document architecture choices, patterns, trade-offs, and pitfalls.

It catches broken or untested work before release and prevents documentation from claiming a feature is ready when verification has failed. The wiki step only runs after the checks pass.

verify — Skill for Claude Code and Codex by fokkerone: A final verification workflow for a completed software feature.

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/fokkerone/superspecs/verify

Any agent

npx skills add fokkerone/superspecs --skill verify

Clone the repo

git clone --depth 1 https://github.com/fokkerone/superspecs

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fokkerone/superspecs/verify.svg)](https://agentmods.dev/skills/fokkerone/superspecs/verify)

Your own site

<a href="https://agentmods.dev/skills/fokkerone/superspecs/verify"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/verify.svg" alt="Measured on agentmods" height="20"></a>

Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,993 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.

Model	Per session	Once invoked
Fable 5.1	$0.00091	$0.02993
Opus 5	$0.00046	$0.01496
Sonnet 5	$0.00018	$0.00599
Haiku 4.5	$0.00009	$0.00299

Measured 5d ago against content hash 4f3fac6b5350, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

.skills/verify/SKILL.md · 438 lines

How it starts

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

Skill: verify

You are doing the final verification before the feature can be shipped.

Execution is complete. This skill runs in two sequential stages:

Stage 1 — Check Tests: confirm the implementation works
Stage 2 — Wiki Import: distill the knowledge

Gate: If Stage 1 fails for any reason — failing tests, skipped tests, uncovered scenarios — stop. Do not proceed to Stage 2. Fix first.

Stage 1 — Check Tests

1. Run the full test suite

<test-runner>

Expected output: all tests passing, zero failing, zero skipped.

Report the result:

Test suite: <date>

Total:   <N>
Passing: <N>  ✅
Failing: <N>  ❌
Skipped: <N>  ⚠️
Pending: <N>  ⚠️

If anything is failing, skipped, or pending: stop. Report. Do not proceed.

2. Verify spec scenario coverage

Read superspec/specs/<slug>/spec.md. For every scenario:

Search the test files for a test covering that scenario. Use the GIVEN/WHEN/THEN as search anchors.

## Spec Coverage Report

### Requirement: <Name>

#### Scenario: <Name>
Status: ✅ covered
Test: `<test-file>:<line>` — `<test name>`

#### Scenario: <Edge case name>
Status: ❌ NOT COVERED
Action required: Write a test for this scenario

[...]

## Summary
Scenarios total: <N>
Covered: <N>  ✅
Missing: <N>  ❌

If any scenario is uncovered: this is a Critical gap. Write the missing test before proceeding.

3. Run tests with coverage (if available)

If the project has a coverage tool:

<coverage-tool> <test-runner>

Note:

Overall coverage %
Coverage of files touched by this feature
Any significant uncovered branches

Coverage is informational — it informs judgment, but 100% coverage is not required. Scenario coverage (step 2) is required.

4. Check for regressions

Compare with baseline if available. Specifically check:

Areas of the codebase adjacent to what was changed
Integration points (APIs called, events emitted, etc.)

If any tests that were passing before this spec's execution are now failing: that's a regression. It must be fixed before proceeding.

Read the full file on GitHub · 438 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.

5d ago First seen · 438 lines · 0 tokens per session scan A 4f3fac6b5350

Subscribe to this mod's changes

verify is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 2,993 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-31.

Memory and context Testing

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

agent-memory

../../../engineering/agent-memory/skills/agent-memory/SKILL.md.

alirezarezvani/claude-skills · 0 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens