yolo-verify

yolo-verify is a skill for Claude Code from CoriChui/yolo. It costs 62 tokens per session (447 once invoked), scanned A, original, MIT.

A verification workflow that checks completed feature work against its stated success criteria.

In plain words
What is it for?
Running the recorded lint and test commands, checking each success criterion, and writing a verification report.
Why use it?
It provides evidence for whether the feature is actually complete instead of relying on an informal review.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the yolo plugin — 11 skills, 1 command 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/corichui/yolo/yolo-verify
Any agent
npx skills add CoriChui/yolo --skill yolo-verify
Clone the repo
git clone --depth 1 https://github.com/CoriChui/yolo

Made for: Claude Code.

Or install yolo, the plugin that ships this one along with the rest of its 11 skills, 1 command.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/corichui/yolo/yolo-verify.svg)](https://agentmods.dev/skills/corichui/yolo/yolo-verify)
Your own site
<a href="https://agentmods.dev/skills/corichui/yolo/yolo-verify"><img src="https://agentmods.dev/badge/skills/corichui/yolo/yolo-verify.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 447 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.1 $0.00062 $0.00447
Opus 5 $0.00031 $0.00224
Sonnet 5 $0.00012 $0.00089
Haiku 4.5 $0.00006 $0.00045

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

Security

Grade A, and why

yolo-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 6d 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.

.claude/skills/yolo-verify/SKILL.md · 26 lines

What it actually says

yolo-verify

Decide, with evidence, whether the work satisfies the brief's success_criteria.

Inputs

  • workspace/features/<slug>/brief.md (success_criteria), the diff git diff <base_branch>...feature/<slug> (three-dot — only what the branch introduced; see .claude/yolo/conventions.md), and plan.md lint_commands/test_commands.

Procedure

  1. Run the recorded lint_commands and test_commands. Capture pass/fail and key output.
  2. For EACH criterion in success_criteria, gather concrete evidence (a passing test, an observed behavior, a code reference). Mark it met/unmet.
  3. Write workspace/features/<slug>/verification.md: one section per criterion with its evidence, plus the lint/test results.

Outcome

  • All criteria met → commit the verification file with the trailer: git add workspace/features/<slug>/verification.md && git commit -m "yolo: verify <slug>" --trailer "YOLO-Verified: true"
  • Any criterion unmet → write the file recording what failed, do NOT write the trailer, and report the gap so execution can resume. A feature is never "done" without YOLO-Verified: true (.claude/yolo/conventions.md). The execute→verify loop is bounded (.claude/yolo/conventions.md The two gates); after repeated failure the caller should stop and escalate to the human rather than re-running, since that signals the plan or criteria need rethinking.

Constraints

  • The only file you write is verification.md. You do not edit code.
  • Verification is semantic (criteria), distinct from CI (mechanical) — yolo-finish handles CI.
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. 6d ago First seen · 26 lines · 62 tokens per session scan A 73b8371980e1

Subscribe to this mod's changes

yolo-verify is a skill published in the GitHub repository CoriChui/yolo (9 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 447 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.

Related

Other skills, from other repositories

create-kr-patch

Use for Korean (Hangul) fan translations of retro console or PC games, including ROM or disc analysis, text-engine reverse engineering, Hangul fonts and custom encodings, script extraction and reinsertion, code hooks, reproducible product builds, and emulator verification. Apply it to new investigations and follow-up…

mcpads/create-retro-game-kr-patch · 109 tokens

0xarchive

Query historical and real-time crypto market data from 0xArchive across two top-level venue APIs: Hyperliquid and Lighter.xyz. HIP-3 builder perps live under the Hyperliquid namespace at /v1/hyperliquid/hip3. HIP-4 outcome markets (binary prediction markets like 'Will BTC be >= X by date Y?') live at…

0xArchiveIO/0xarchive-skill · 310 tokens

make-brief

Produce a local HTML page a human can actually read and decide from - a narrative decision brief, an item-by-item technical review page, or a mechanism explainer that walks through a system and its terminology. Triggers when the user says "write this up as an HTML page for me", "I don't follow, give me the full…

WatsonTsai/smart-brief · 0 tokens

quiz-me

Quiz the user on root cause and intended fix BEFORE writing any non-trivial code, then verify comprehension of every change after. Use when the user asks for a bug fix, refactor, or feature and wants to stay technically sharp instead of vibe-coding. Also use when the user says "quiz me", "don't let me vibe code", or…

emanzurv/quiz-me-skill · 82 tokens

slopmop

Trigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to sm swab, sm scour, sm buff, sm sail, sm refit, or sm doctor so remediation follows the established rails. Also trigger when asked to "install" or "set up" slop-mop in a repo, or when you find a repo with sm…

ScienceIsNeato/slop-mop · 186 tokens

markup-mode

Add a frontend-only review/markup layer to any HTML artifact, Markdown document, or live UI so a reviewer can anchor comments to specific text or specific elements, then compile them into tagged Markdown for an agent to act on. Use when the user wants to "mark up this page", "add a review/comment layer", "annotate…

spunt/markup-mode · 146 tokens