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 skills add sefaertunc/Worclaude --skill verificationgit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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.
[](https://agentmods.dev/skills/sefaertunc/worclaude/verification)<a href="https://agentmods.dev/skills/sefaertunc/worclaude/verification"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/verification/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.
<a href="https://agentmods.dev/skills/sefaertunc/worclaude/verification"><img src="https://agentmods.dev/badge/skills/sefaertunc/worclaude/verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00018 | $0.01123 |
| Opus 5.5 | $0.00007 | $0.00449 |
| Sonnet 5.5 | $0.00004 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
verification scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:3000/api/resource \ How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification
Note: The bash examples below are reference snippets. If you enable
disableSkillShellExecutionin Claude Code settings (v2.1.101+), any inline shell execution from skills is blocked. These fenced examples are safe to read; copy-paste them into your terminal to run.
Beyond Unit Tests
Unit tests verify code logic. Verification confirms the feature actually works in its real environment. Both are necessary. Neither alone is sufficient.
The /verify command runs automated checks, but domain-specific verification often requires manual steps or specialized tooling.
Closing the Feedback Loop
Every change needs a feedback loop: make a change, verify it worked, then move on. The loop must be closed BEFORE committing.
Bad workflow: change code -> commit -> move to next task -> discover it's broken Good workflow: change code -> verify -> commit -> move to next task
Web Application Verification
After changing UI or API behavior:
- Start the dev server
- Navigate to the affected page/endpoint
- Test the happy path manually
- Test at least one error path
- Check browser console for errors/warnings
- Verify responsive behavior if UI changed
For API changes:
# Test the endpoint directly
curl -X POST http://localhost:3000/api/resource \
-H "Content-Type: application/json" \
-d '{"field": "value"}'
# Check response status and body
API Verification
Test beyond the happy path:
- Valid request with all fields
- Valid request with minimum fields
- Invalid request (missing required field)
- Invalid request (wrong types)
- Authentication failures
- Rate limiting behavior
- Concurrent request handling (if relevant)
Use curl, httpie, or the project's API test suite. Automate what you can, but do at least one manual check of the actual running server.
CLI Verification
After changing CLI behavior:
- Run the command with typical arguments
- Run with edge case arguments (empty, very long, special characters)
- Run with invalid arguments (verify error messages are helpful)
- Test piping and redirection if applicable
- Verify exit codes
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.
- 1mo ago First seen · 146 lines · 18 tokens per session scan A 4588ce0284ea
verification is a skill published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,123 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
omh-agent-evaluation
This is a Hermes-native agent-evaluation workflow skill.
omh-verification-gate
This is an OMH verification-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.