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.
git clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/kryptobaseddev/cleo/verify-work)<a href="https://agentmods.dev/commands/kryptobaseddev/cleo/verify-work"><img src="https://agentmods.dev/badge/commands/kryptobaseddev/cleo/verify-work.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.1 | $0.00013 | $0.00339 |
| Opus 5 | $0.00006 | $0.00169 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
gsd:verify-work 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- gsd:verify-work — 88% identical, 13 lines differ
- gsd:verify-work — 88% identical, 8 lines differ
- gsd:verify-work — 83% identical, 6 lines differ
What it actually says
Purpose: Confirm what Claude built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /gsd-execute-phase
<execution_context> @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/workflows/verify-work.md @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/templates/UAT.md </execution_context>
Context files are resolved inside the workflow (init verify-work) and delegated via <files_to_read> blocks.
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 · 39 lines · 13 tokens per session scan A b7001b506d9c
gsd:verify-work is a command published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 17d ago), licensed MIT. It adds 13 tokens to every session and 339 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-09-03.
Other commands, from other repositories
paul:verify
Guide manual user acceptance testing of recently built features.
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.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
journey-audit
Outside-in product audit as a deep session — 7 read-only roles check what the site promises against what the code does, what a user experiences, what arrives by mail, and what the data says is used. Writes a dossier; needs a per-repo journey-manifest.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.