What is verify-tests?

A final test-checking procedure that runs the full test suite and compares tests with every scenario in a feature specification. A test suite is the complete collection of automated checks for a project.

It helps verify that all tests pass and that each requirement scenario has a corresponding test.

It catches failing, skipped, pending, or undocumented scenarios before a feature is declared complete.

How fokkerone/superspecs configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to fokkerone/superspecs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/fokkerone/superspecs/main/.skills/verify-tests/SKILL.md

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-tests.svg)](https://agentmods.dev/skills/fokkerone/superspecs/verify-tests)

Your own site

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

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

When invoked 853 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00062	$0.00853
Opus 5	$0.00031	$0.00426
Sonnet 5	$0.00012	$0.00171
Haiku 4.5	$0.00006	$0.00085

Measured 7d ago against content hash 673cd6d57bc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

verify-tests 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 7d 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-tests/SKILL.md · 154 lines

How it starts

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

Skill: verify-tests

You are doing the final test verification before the feature can be declared done.

Execution is complete. Now you verify everything works before moving to wiki and ship.

Steps

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

5. Update status.md

If all checks pass:

## Phase
3.1 — Verify › Check Tests ✅

## Test Results
- Suite: X passing, 0 failing, 0 skipped
- Spec scenarios: Y/Y covered
- Regressions: none

## Checklist
...
- [x] All tests passing
- [x] Code review passed (no Critical findings)
- [ ] Wiki imported
...

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

7d ago First seen · 154 lines · 62 tokens per session scan A 673cd6d57bc5

Subscribe to this mod's changes

verify-tests is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 853 once invoked, about $0.0003 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

superspecs: Skill for Claude Code