verify

verify is a skill for Claude Code, Codex from sd0xdev/sd0x-harness. It costs 17 tokens per session (1,086 once invoked), scanned A, original, MIT.

A verification workflow that runs available linting, type checks, unit tests, integration tests, and end-to-end tests.

In plain words
What is it for?
Use it to verify code quality, types, automated tests, and full user flows after a change.
Why use it?
It checks different parts of a codebase so problems can be found before changes are considered complete.

Skill for Claude CodeCodex

Part of the sd0x-dev-flow plugin — 98 skills, 16 agents, 5 hooks 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/sd0xdev/sd0x-harness/verify
Any agent
npx skills add sd0xdev/sd0x-harness --skill verify
Clone the repo
git clone --depth 1 https://github.com/sd0xdev/sd0x-harness

Made for: Claude Code, Codex.

Or install sd0x-dev-flow, the plugin that ships this one along with the rest of its 98 skills, 16 agents, 5 hooks.

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 verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/verify.svg)](https://agentmods.dev/skills/sd0xdev/sd0x-harness/verify)
Your own site
<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/verify"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,086 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.00017 $0.01086
Opus 5 $0.00009 $0.00543
Sonnet 5 $0.00003 $0.00217
Haiku 4.5 $0.00002 $0.00109

Measured 2d ago against content hash ee4a9acf7a66, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 114 lines

How it starts

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

Verification Loop

Trigger

  • Keywords: verify, run tests, check, lint, typecheck, verification

When NOT to Use

  • Pre-commit gate (use /precommit or /precommit-fast)
  • Test coverage review (use /codex-test-review)
  • Running a single specific test (run directly)

Workflow Steps

Step Goal Safety Skip if Missing
lint Check code style (read-only) read-only yes
typecheck Static type checking (full only) read-only yes
test-unit Run unit test suite read-only yes
test-integration Run integration tests (full only) read-only yes
test-e2e Run end-to-end tests (full only) read-only yes

Failure behavior: continue-all (run all steps, report all results)

Task

Step 1: Check for runner script

Use Glob to check if .claude/scripts/verify-runner.js exists in the project root.

  • Found → run: node .claude/scripts/verify-runner.js $ARGUMENTS
    • If runner succeeds, use its output and skip to the Output section.
    • If runner fails, treat as a real verification failure (do not silently fallback).
  • NOT found → skip to Step 2 (do NOT attempt to run the runner).

Step 2: Fallback (no runner script)

If the runner was not found in Step 1, detect the project ecosystem to run steps manually.

Ecosystem detection (check project root for manifest files):

Manifest Ecosystem Lint Typecheck Test
package.json Node.js {pm} lint {pm} typecheck {pm} test:unit
pyproject.toml Python ruff check . mypy . pytest
Cargo.toml Rust cargo clippy (implicit) cargo test
go.mod Go golangci-lint run go vet ./... go test ./...
build.gradle Java ./gradlew spotlessCheck (implicit) ./gradlew test

For Node.js projects, auto-detect package manager from lockfile.

$ARGUMENTS == "fast": lint + unit only

Read the full file on GitHub · 114 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. 2d ago First seen · 114 lines · 17 tokens per session scan A ee4a9acf7a66

Subscribe to this mod's changes

verify is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,086 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-09-03.

Related

Other skills, from other repositories

check-and-test

Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…

ReflexioAI/claude-smart · 97 tokens

testing-strategies

Comprehensive testing strategy covering unit, integration, e2e, property-based, and mutation testing with practical patterns.

cosmicstack-labs/mercury-agent-skills · 27 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

frontend-testing

Comprehensive frontend testing strategy covering unit, integration, E2E, visual regression, and accessibility testing.

cosmicstack-labs/mercury-agent-skills · 23 tokens

testing

Writes and documents the test suite for a generated cli-web- CLI (Phase 3): unit tests with mocked HTTP, live E2E tests, subprocess tests via resolvecli, and the TEST.md plan/results record. Use after the methodology skill completes implementation.

ItamarZand88/CLI-Anything-WEB · 55 tokens

test-implement

Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.

shinpr/claude-code-workflows · 48 tokens