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.
npx agentmods add skills/iwritec0de/wp-dev/verificationnpx skills add iwritec0de/wp-dev --skill verificationgit clone --depth 1 https://github.com/iwritec0de/wp-devWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00059 | $0.00918 |
| Opus 5 | $0.00030 | $0.00459 |
| Sonnet 5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
verification 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Skill
Evidence before claims, always. NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION.
Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE. If you have not run the verification command in the current session, you cannot claim it passes. Prior knowledge, assumptions, and memory of previous runs do not count. Only fresh output from the current session constitutes evidence.
The Five-Step Gate
Every completion claim must pass through this gate:
- Identify — Determine which command proves your claim. "Tests pass" requires running the test suite. "No lint errors" requires running the linter. "It builds" requires running the build.
- Execute — Run the command freshly. Not from memory. Not from a previous session. Right now, in the current session.
- Read — Read the FULL output. Do not skim. Do not assume. If the output is long, read all of it. Errors can hide at the end.
- Verify — Confirm the output actually supports your claim. A test suite that prints results but exits with a failure code does not pass. A build that emits warnings about missing dependencies is not clean.
- Assert — Only after steps 1-4 are complete, state your claim and include the evidence. Quote the relevant output.
WordPress/PHP Verification Checklist
Before claiming work is complete in this project, run each applicable command and confirm clean output:
| Check | Command | What it proves |
|---|---|---|
| Tests | vendor/bin/phpunit |
All unit and integration tests pass |
| Coding standards | vendor/bin/phpcs --standard=WordPress . |
Code conforms to WordPress coding standards |
| Syntax check | php -l *.php |
No PHP syntax errors in changed files |
| WordPress loads | wp eval 'echo "OK";' |
WordPress boots without fatal errors |
| Clear caches | wp cache flush and wp transient delete --all |
Stale cache is not masking issues |
Run these in order. A syntax error caught by php -l is cheaper to fix than one discovered by PHPUnit. Coding standards violations are cheaper to fix before tests run. Always clear caches before final verification to ensure you are testing real behavior, not cached results.
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.
- yesterday First seen · 69 lines · 59 tokens per session scan A d968222318e9
verification is a skill published in the GitHub repository iwritec0de/wp-dev (1 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 918 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…