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 commands/sefaertunc/worclaude/verifygit 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/commands/sefaertunc/worclaude/verify)<a href="https://agentmods.dev/commands/sefaertunc/worclaude/verify"><img src="https://agentmods.dev/badge/commands/sefaertunc/worclaude/verify.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00410 |
| Opus 5 | $0.00008 | $0.00205 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
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 3d 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.
What it actually says
Run the project's fast read-only verification suite.
When invoked with arguments, use them to scope what to verify. Example: /verify just the auth module
Arguments: $ARGUMENTS
Scope (locked)
/verify is intentionally narrow:
- Run the test suite — the project's primary test runner
- Run the linter — fail on any lint error
- Optional:
prettier --check(or equivalent format check) — read-only format drift detection. Skip if the project does not use a format checker.
That is the entire scope. Report results clearly. Do not proceed if any check fails.
Read-only contract
/verify MUST NOT modify files. No formatter auto-fix, no test fixture
regeneration, no --fix-style flags. If a tool would write anything to disk
during a check, find the read-only equivalent (e.g., prettier --check not
prettier --write, eslint not eslint --fix).
What is NOT in /verify
- Build — slow and not a "drift check." Use
/build-fixif the build is broken. - Type checking — covered by the
stricthook profile's PostToolUse hook for projects that want it on every edit. Not part of the standard /verify contract. - Domain-specific end-to-end verification — that is the
verify-appagent's job, invoked separately when needed.
This narrow scope is deliberate: /verify is the fast feedback loop. Adding more checks slows it down and erodes the "run before every commit" habit.
Trigger Phrases
- "verify everything"
- "run all checks"
- "is this working"
- "test and lint"
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.
- 3d ago First seen · 48 lines · 16 tokens per session scan A 26238450fc60
verify is a command published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 410 once invoked, about $0.0001 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 commands, from other repositories
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
generate-rules
Generate development rules and standards into RULES.md.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.