verify

verify is a skill for Claude Code, Codex from SirhanMacx/Claw-ED. It costs 52 tokens per session (1,600 once invoked), scanned A, a copy of Skill: Verify skill, MIT.

A hands-on verification guide for checking that a code change works when the application runs. It uses observed application behavior as evidence instead of relying only on reading code or rerunning automated checks.

In plain words
What is it for?
Use it to verify pull requests, fixes, and local changes by building and running the app, reaching the changed behavior, and recording what happens.
Why use it?
It prevents false confidence from tests or type checks that pass while the real feature still fails during use.

Skill for Claude CodeCodex

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/sirhanmacx/claw-ed/verify
Any agent
npx skills add SirhanMacx/Claw-ED --skill verify
Clone the repo
git clone --depth 1 https://github.com/SirhanMacx/Claw-ED

Made for: Claude Code, Codex.

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/sirhanmacx/claw-ed/verify.svg)](https://agentmods.dev/skills/sirhanmacx/claw-ed/verify)
Your own site
<a href="https://agentmods.dev/skills/sirhanmacx/claw-ed/verify"><img src="https://agentmods.dev/badge/skills/sirhanmacx/claw-ed/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,600 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 98% copy Near-identical to another mod 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.00052 $0.01600
Opus 5 $0.00026 $0.00800
Sonnet 5 $0.00010 $0.00320
Haiku 4.5 $0.00005 $0.00160

Measured 5d ago against content hash a9995acc78b2, 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 5d 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.

Origin

This is a copy

98% identical to Skill: Verify skill — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cli/source/src/skills/bundled/verify/SKILL.md · 163 lines

How it starts

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

Verification is runtime observation. You build the app, run it, drive it to where the changed code executes, and capture what you see. That capture is your evidence. Nothing else is.

Don't run tests. Don't typecheck. CI ran both before you got here — green checks on the PR mean they passed. Running them again proves you can run CI. Not as a warm-up, not "just to be sure," not as a regression sweep after. The time goes to running the app instead.

Don't import-and-call. import { foo } from './src/...' then console.log(foo(x)) is a unit test you wrote. The function did what the function does — you knew that from reading it. The app never ran. Whatever calls foo in the real codebase ends at a CLI, a socket, or a window. Go there.

Find the change

Establish the full range first — a branch may be many commits:

git log --oneline @{u}..              # count commits
git diff @{u}.. --stat                # full range, not HEAD~1
gh pr diff                            # if in a PR context

State the commit count in your report. Large diff truncating? Redirect: git diff @{u}.. > /tmp/d then Read it. No diff at all → say so, stop.

The diff is ground truth. The PR description is a claim about it. Read both. If they disagree, that's a finding.

Surface

The surface is where a user — human or programmatic — meets the change. That's where you observe.

Change reaches Surface You
CLI / TUI terminal type the command, capture the pane — example
Server / API socket send the request, capture the response — example
GUI pixels drive it under xvfb/Playwright, screenshot
Library package boundary sample code through the public export — import pkg, not import ./src/...
Prompt / agent config the agent run the agent, capture its behavior
CI workflow Actions dispatch it, read the run

Internal function? Not a surface. Something in the repo calls it and that caller ends at one of the rows above. Follow it there. A bash security gate's surface isn't the function's return value — it's the CLI prompting or auto-allowing when you type the command.

Read the full file on GitHub · 163 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 5d ago First seen · 163 lines · 52 tokens per session scan A a9995acc78b2

Subscribe to this mod's changes

verify is a skill published in the GitHub repository SirhanMacx/Claw-ED (58 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,600 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to Skill: Verify skill, differing in 5 lines, and is treated as a copy.

Related

Other skills, from other repositories

moodle-behat-testing

Use when writing or running Behat acceptance tests for Moodle plugins. Covers feature files, custom step definitions, tags, data generators in Background, JavaScript scenarios, and Selenium/Chromedriver setup.

SaadRahman01/claude-moodle-dev · 45 tokens

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

run-integration-tests

Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.

dotnet/maui · 35 tokens

cli-e2e-testcase-writer

Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.

larksuite/cli · 78 tokens

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

every-app/open-seo · 35 tokens

harness-test-writer

Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…

maximhq/bifrost · 133 tokens