spec-verify SKILL.md skillA

spec-verify from kamioj/spec-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kamioj/spec-workflow/spec-verify@git:20260921.886d28d

Pins git:20260921.886d28d in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: kamioj/spec-workflow
Path: codex/skills/spec-verify/SKILL.md
Versions recorded: 6
Latest version: git:20260921.886d28d, committed Sep 21, 2026
First version recorded: Aug 22, 2026
Size: 15,067 bytes
Repository stars: 20
License: a license file GitHub does not identify

Verifies the current change by dispatching the independent spec-verifier agent (fresh context — the implementing conversation never audits itself) across four dimensions (Completeness / Correctness / Coherence incl. the charter sub-audit / Reuse & Conformance). Every run updates the verification ledger spec/changes/<name>/verify.md (stable finding IDs + round diffing + unfixed-escalation). Can be re-run independently.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

<!-- GENERATED from core/commands/verify.md — edit the core file and run node tools/generate.mjs; hand edits will be overwritten -->

# $spec-verify

> Heterogeneous peer review (`--codex`) is not available in this port — Codex cannot be its own heterogeneous reviewer.

This command takes no flags on this host. **Any token in the arguments is flagged to the user as a possible typo** — nothing is silently ignored.

## Independent verifier (why verify dispatches an agent instead of reviewing inline)

The conversation that just ran `$spec-apply` cannot audit its own output — same context, same blind spots, and "be objective" instructions have near-zero measured effect on self-preference. `$spec-verify` therefore **spawns the spec-verifier agent (defined in ~/.codex/agents/spec-verifier.toml)** (fresh context: it reads only proposal + design + charter + the diff) and keeps the bookkeeping for itself. The same rule binds `$spec-apply`'s closing verification: the review is ALWAYS performed by a spawned spec-verifier, whoever initiates it — the implementing conversation only ever does bookkeeping:
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kamioj/spec-workflow/spec-verify@sha256:35577b4a5bebbf70

The line at the top of this page pins the label git:20260921.886d28d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_54j6wbpstupfqjuh.svg)](https://markdownregistry.com/a/art_54j6wbpstupfqjuh)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 6 versions of this file, between Aug 22, 2026 and Sep 21, 2026, about one every 6 days.

version	committed	commit	size	audit
git:20260921.886d28d latest	2026-09-21	886d28d	15,067 B	A	view · diff
git:20260910.a57f970	2026-09-10	a57f970	14,415 B	A	view · diff
git:20260904.ec4059d	2026-09-04	ec4059d	14,225 B	A	view · diff
git:20260904.f4c79c8	2026-09-04	f4c79c8	14,106 B	A	view · diff
git:20260825.2f8fabe	2026-08-25	2f8fabe	14,214 B	A	view · diff
git:20260822.e5fde5b	2026-08-22	e5fde5b	13,236 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (15067 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

kamioj/spec-workflow · 20 stars · license a license file GitHub does not identify · pushed 2026-09-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_54j6wbpstupfqjuh
GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/spec-verify
GET https://markdownregistry.com/api/v1/blob/35577b4a5bebbf70673593dee87904ba78cfa71288165158f8a876e99b5ae4d7

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.