create-verification-skill

create-verification-skill is a skill for Claude Code from Yeachan-Heo/oh-my-claudecode. It costs 45 tokens per session (852 once invoked), scanned A, original, MIT.

A project-specific verification procedure built by discovering and running the repository's real build, test, lint, type-check, formatting, development-server, and end-to-end commands. It records what each check covers and what a passing result looks like.

In plain words
What is it for?
It helps set up a local verification skill once per repository and earn an initial verdict from real results. It also records runtime details, environment requirements, known issues, and safe read-only forms of formatting checks.
Why use it?
Generic verification instructions may guess the wrong commands for a repository. Running and documenting the actual commands creates reliable checks for future work, including manual checks that cannot be automated.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the oh-my-claudecode plugin — 83 skills, 21 commands, 19 agents, 11 hooks, 1 MCP server shipped together

Good fit It helps set up a local verification skill once per repository and earn an initial verdict from real results. It also records runtime details, environment requirements, known issues, and safe read-only forms of formatting checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yeachan-heo/oh-my-claudecode/create-verification-skill
About the project

Oh My Claude Code is a multi-agent orchestration system for Claude Code, coordinating specialized agents, commands, skills, hooks, and workflows. It is designed for developers who want Claude Code to handle coding tasks through coordinated agent roles. Catalogue entries are components of its Claude Code workflow, including agents, commands, skills, hooks, instructions, MCP configuration, and a plugin.

Yeachan-Heo/oh-my-claudecode · 40,685 stars · on GitHub · oh-my-claudecode.dev

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.

Any agent
npx skills add Yeachan-Heo/oh-my-claudecode --skill create-verification-skill
Clone the repo
git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode

Made for: Claude Code.

Or install oh-my-claudecode, the plugin that ships this one along with the rest of its 83 skills, 21 commands, 19 agents, 11 hooks, 1 MCP server.

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 create-verification-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/create-verification-skill/github.svg)](https://agentmods.dev/skills/yeachan-heo/oh-my-claudecode/create-verification-skill)
Your own site
<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-claudecode/create-verification-skill"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/create-verification-skill/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-verification-skill

Your own site · 80×15
<a href="https://agentmods.dev/skills/yeachan-heo/oh-my-claudecode/create-verification-skill"><img src="https://agentmods.dev/badge/skills/yeachan-heo/oh-my-claudecode/create-verification-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 852 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00852
Opus 5.5 $0.00018 $0.00341
Sonnet 5.5 $0.00009 $0.00170
Haiku 4.5 $0.00005 $0.00085

Measured today against content hash 184d4240c471, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-verification-skill 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 today.

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/create-verification-skill/SKILL.md · 70 lines

How it starts

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

Create Verification Skill

The bundled verify skill demands evidence but cannot know this repo's commands. This skill generates the project-local verify skill that makes verification concrete — by discovering the commands through execution, not by guessing from a README.

When to use

  • a repo has no .claude/skills/verify/ and work will be verified here more than once
  • the generic verification flow keeps guessing commands wrong for this repo

Workflow

  1. Discover by running. For each candidate surface — build, test, lint, typecheck, format, dev server, e2e — find the command (package scripts, Makefile, CI config) and run it. Record the real invocation, the expected passing output shape, the runtime, and the known gotchas (env vars, seed data, order dependence). A command you have not run is a hypothesis, not a check. Write-mode formatters (prettier --write, eslint --fix) mutate tracked files — record the read-only check form (prettier --check, eslint --check) as the verification command, never the mutating one.
  2. Record the manual surface. What cannot be checked by command here: the pages or flows a human (or run/visual-verdict) exercises, and what "looks right" means for each.
  3. Write the feature map. A table of what each check actually covers — which entry points, which layers, what it cannot see. The map is the skill's honesty: verification strength is knowable, not assumed.
  4. Generate .claude/skills/verify/SKILL.md containing: the exact commands with expected outcomes, the manual checks, the feature map, and the escalation path (which failure means what, who owns it). Keep it short enough that a fresh session reads it whole. If a verify skill already exists at the canonical root (.omc/skills/verify/SKILL.md or .claude/skills/verify/SKILL.md), respect it: update its commands and feature map in place rather than overwriting, and say what changed.
  5. Prove it. Run the generated skill's own flow once end to end on a real change and record the result through the ledger's locked writer — appendLedgerEntry and defaultLedgerPath from the installed package's dist/features/verification-ledger/index.js (babysit's ledger step demonstrates the exact invocation); never append raw rows to .omc/state/verification-ledger.tsv — the writer owns header creation, locking, and cell sanitization. The verdict is the one the flow actually earned: a real UI exercised is live-ui-verified, a test suite run is unit-test-verified, only build/lint/typecheck passed is type-check-only, and nothing runnable is no positive row at all.

Read the full file on GitHub · 70 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. today First seen · 70 lines · 45 tokens per session scan A 184d4240c471

Subscribe to this mod's changes

create-verification-skill is a skill published in the GitHub repository Yeachan-Heo/oh-my-claudecode (40,685 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 852 once invoked, about $0.0002 per session on Opus 5.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-11-08.

Related

create-verification-skill compared with skills from other repositories

create-verification-skill next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-verification-skillYeachan-Heo/oh-my-claudecodeSkill41ktodayMITA45Claude Code
moai-ref-testing-pyramidmodu-ai/moai-adkSkill1.3ktodayApache-2.0A61Claude Code
reality-verificationtzachbon/smart-ralphSkill56712d agoMITA81Claude Code
moai-e2emodu-ai/moai-adkSkill1.3ktodayApache-2.0A29Claude Code
horizon-app-testingpeters/horizonSkill721todayMITA48Claude Code
smoke-checkstriderZA/OpenCodeGameStudiosSkill1183d agoMITA61Claude Code
blueprint-from-collection-acceptancereceptron/mulmoterminalSkill261yesterdayMITA41Claude Code, Codex