Agent skill

Verify

Verification loop — lint - typecheck - unit - integration - e2e

MITAuto-check passedTesting & QA

Install Verify

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verify .claude/skills/verify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "verify" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/verify into .claude/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/sd0xdev/sd0x-harness/tree/main/skills/verify

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill verify -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness verify --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/verify .agents/skills/verify && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "verify" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/verify into .agents/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill verify -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness verify --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/verify .cursor/skills/verify && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "verify" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/verify into .cursor/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/sd0xdev/sd0x-harness.git --path skills/verify

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill verify -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness verify --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/verify .gemini/skills/verify && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "verify" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/verify into .gemini/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness verify

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill verify -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/verify .github/skills/verify && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "verify" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/verify into .github/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill verify -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness verify --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/verify .opencode/skills/verify && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "verify" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/verify into .opencode/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: verify
GitHub stars: 192
Token cost: ~1.2k tokens
SKILL.md length: 508 words
Files: 1
Skills in repo: 91
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Verification loop — lint - typecheck - unit - integration - e2e

Works in 2 steps: Check for runner script → Fallback (no runner script)
Tasks that involve End-to-end testing
SKILL.md covers Trigger, When NOT to Use, Commit Context and Workflow Steps, plus 2 more sections
Calls node, cargo and go

What it does

Verify is an agent skill from sd0xdev/sd0x-harness. Verification loop — lint - typecheck - unit - integration - e2e

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing and Linting and formatting. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.

When your agent uses it

Tasks that involve End-to-end testing
Tasks that involve Linting and formatting

Example prompts

“/verify”

Requirements

Python 3
Node.js
Pre-approved tools (allowed-tools): Bash(node:*), Bash(pnpm:*), Bash(yarn:*), Bash(npm:*), Bash(npx:*), Bash(git:*), Bash(python*:*), Bash(pytest:*), Bash(ruff:*), Bash(mypy:*), Bash(cargo:*), Bash(go:*), Bash(golangci-lint:*), Bash(./gradlew:*), Bash(mvn:*), Bash(bundle:*), Read, Grep, Glob

Workflow steps

2 steps, taken from the step headings in SKILL.md.

Check for runner script
Fallback (no runner script)

What it can do on your machine

Read from SKILL.md and the folder at commit c9a2036. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(node:*)
- Bash(pnpm:*)
- Bash(yarn:*)
- Bash(npm:*)
- Bash(npx:*)
- Bash(git:*)
- Bash(python*:*)
- Bash(pytest:*)
- Bash(ruff:*)
- Bash(mypy:*)
…and 9 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- node
- cargo
- go
- ruff
- mypy
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify loads about 1.2k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 508 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~19
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sd0xdev/sd0x-harness at commit c9a2036, republished under its MIT licence (© sd0xdev). 508 words, ~1,242 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder).

name: verify
description: Verification loop — lint -> typecheck -> unit -> integration -> e2e
allowed-tools: Bash(node:*), Bash(pnpm:*), Bash(yarn:*), Bash(npm:*), Bash(npx:*), Bash(git:*), Bash(python*:*), Bash(pytest:*), Bash(ruff:*), Bash(mypy:*), Bash(cargo:*), Bash(go:*), Bash(golangci-lint:*), Bash(./gradlew:*), Bash(mvn:*), Bash(bundle:*), Read, Grep, Glob

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)

Commit Context

Claude Code 2.1.286 and later tell Claude to run a skill named verify before a commit. The gate that binds a commit is /precommit (rules/auto-loop.md), so when /verify runs as that pre-commit check it neither repeats a precommit that already passed nor stands in for one that did not:

Read the gate state: node scripts/review-state.js check --format=json, installed copy first (.claude/scripts/review-state.js).
precommit.passed is exactly true → report "Precommit already passed at the current code digest; no new checks executed" and stop. Emit no sentinel and write no verdict note.
Anything else — passed false, no precommit slot, output that does not parse as JSON, or no checker found → run /precommit. Its own report and evidence contract apply; /verify adds no verdict of its own.

passed is content-addressed — noted, at the current tree digest, with verdict pass — so no separate freshness check is needed. Run any other way, /verify performs the steps below unchanged.

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

Show full SKILL.md (203 more words)Show less

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

Otherwise (full): lint -> typecheck -> unit -> integration -> e2e

Step	package.json script	If missing
lint	`lint`	Skip with note
typecheck	`typecheck`	Skip with note
unit	`test:unit`, fallback to `test`	Skip with note
integration	`test:integration`	Skip (requires explicit path)
e2e	`test:e2e`	Skip (requires explicit path)

Graceful Skip Rules

Scenario	Behavior
No `lint` script	Skip, log "no lint script — skipped"
No `typecheck` script	Skip, log "no typecheck script — skipped"
No `test:unit` or `test` script	Skip, log "no test script — skipped"
No `package.json`	Report error, cannot run checks

Output

The last line is ## Verify:, never ## Overall:. ## Overall: is the precommit runner's sentinel alone (rules/auto-loop.md § Gate Sentinels), so a verification report is never read as a precommit verdict.

For fast mode:

markdown

## Verify (fast)

| Step | Status | Notes |
|------|--------|-------|
| lint | ✅/❌/⏭️ | |
| unit | ✅/❌/⏭️ | |

## Verify: ✅ PASS / ❌ FAIL

For full mode:

markdown

## Verify (full)

| Step | Status | Notes |
|------|--------|-------|
| lint | ✅/❌/⏭️ | |
| typecheck | ✅/❌/⏭️ | |
| unit | ✅/❌/⏭️ | |
| integration | ✅/❌/⏭️ | skipped unless path specified |
| e2e | ✅/❌/⏭️ | skipped unless path specified |

## Failures (if any)

- Root cause: <first error>
- Fix: <suggestion>

## Verify: ✅ PASS / ❌ FAIL

Files

Just SKILL.md in skills/verify of sd0xdev/sd0x-harness.

Open the folder on GitHubat commit c9a2036

Compare with similar skills

Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Verify this skillsd0xdev/sd0x-harness	192	—	~1.2k	Automated safety check: Pass	MIT	yesterday
Precommitploxc/modbux	108	—	~1.5k	Automated safety check: Pass	MIT	yesterday
Pierre Testing and Verification Guidepierrecomputer/pierre	6.2k	—	~608	Automated safety check: Pass	Apache-2.0	yesterday
Ha Frontend Testinghome-assistant/frontend	5.7k	—	~1.7k	Automated safety check: Pass	Apache-2.0	today
Acceptance Test Authoringintent-driven-dev/intent-driven-template	159	—	~2k	Automated safety check: Pass	MIT	3 days ago
Mmd Testtogechiyo/MMD_modoki	145	—	~936	Automated safety check: Pass	MIT	yesterday

Similar skills

Precommit
ploxc/modbux
Run the checklist before committing or merging — read the diff, lint, typecheck, the unit suite, the e2e specs the change touches, then report and commit.
108 GitHub stars~1.5k tokensUpdated yesterday
Testing & QAAuto-check passed
Pierre Testing and Verification Guide
pierrecomputer/pierre
Chooses the right verification step after a code change in Pierre's monorepo: format and lint, a typecheck, Bun unit tests, snapshots, or Playwright E2E.
6.2k GitHub stars~608 tokensUpdated yesterday
Testing & QAAuto-check passed
Ha Frontend Testing
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
5.7k GitHub stars~1.7k tokensUpdated today
Testing & QAAuto-check passed
Acceptance Test Authoring
intent-driven-dev/intent-driven-template
A skill your agent uses when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an…
159 GitHub stars~2k tokensUpdated 3 days ago
Testing & QAAuto-check passed
Mmd Test
togechiyo/MMD_modoki
Select and run the smallest sufficient MMDmodoki verification set after code or configuration changes, then separate new failures from known baselines.
145 GitHub stars~936 tokensUpdated yesterday
Testing & QAAuto-check passed
Michel Packmind Engineer Review
PackmindHub/packmind
Review an implemented GitHub issue the way a senior Packmind engineer would — the human-judgment checks that ESLint, the TypeScript compiler, and e2e tests cannot catch (authorization scoping…
317 GitHub stars~2.7k tokensUpdated yesterday
Testing & QAAuto-check passed

Questions about Verify

What does Verify do?

Verification loop — lint - typecheck - unit - integration - e2e. Verify is an agent skill from sd0xdev/sd0x-harness.

When should I use Verify?

Verify fits situations like: tasks that involve End-to-end testing; tasks that involve Linting and formatting.

How do I install Verify in Claude Code?

Run `npx skills add sd0xdev/sd0x-harness --skill verify -a claude-code`. Or copy the skill folder (skills/verify in sd0xdev/sd0x-harness) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.

How do I install Verify in Codex?

Run `npx skills add sd0xdev/sd0x-harness --skill verify -a codex`. Or copy the skill folder (skills/verify in sd0xdev/sd0x-harness) into .agents/skills/verify in your project. Codex loads it when a task matches its description.

Can I use Verify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.

What does Verify need to run?

Going by SKILL.md and its folder, Verify needs the command-line tools its instructions call (node, cargo, go, ruff and mypy). Our summary lists: Python 3; Node.js. Its frontmatter pre-approves these tools: Bash(node:*), Bash(pnpm:*), Bash(yarn:*), Bash(npm:*), Bash(npx:*), Bash(git:*), Bash(python*:*), Bash(pytest:*), Bash(ruff:*), Bash(mypy:*), Bash(cargo:*), Bash(go:*), Bash(golangci-lint:*), Bash(./gradlew:*), Bash(mvn:*), Bash(bundle:*), Read, Grep, Glob.

Does Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verify use?

Verify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify?

Skills that share tags, products or a category with Verify: Precommit (ploxc/modbux, 108 stars), Pierre Testing and Verification Guide (pierrecomputer/pierre, 6.2k stars), Ha Frontend Testing (home-assistant/frontend, 5.7k stars) and Acceptance Test Authoring (intent-driven-dev/intent-driven-template, 159 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 6, 2026.

Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Verify

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Verification Loop

Trigger

When NOT to Use

Commit Context

Workflow Steps

Task

Step 1: Check for runner script

Step 2: Fallback (no runner script)

Graceful Skip Rules

Output

Files

Compare with similar skills

Similar skills

More from sd0xdev/sd0x-harness

Related

Questions about Verify