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/validate-phase)<a href="https://agentmods.dev/commands/kryptobaseddev/cleo/validate-phase"><img src="https://agentmods.dev/badge/commands/kryptobaseddev/cleo/validate-phase/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/commands/kryptobaseddev/cleo/validate-phase"><img src="https://agentmods.dev/badge/commands/kryptobaseddev/cleo/validate-phase.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.00019 | $0.00238 |
| Opus 5.5 | $0.00008 | $0.00095 |
| Sonnet 5.5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
gsd:validate-phase 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 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.
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
5 near-identical copies found in the catalogue:
- gsd:validate-phase — 89% identical, 4 lines differ
- gsd:validate-phase — 84% identical, 7 lines differ
- gsd:validate-phase — 84% identical, 4 lines differ
- gsd:validate-phase — 81% identical, 4 lines differ
- gsd-validate-phase — 73% identical, 9 lines differ
What it actually says
Output: updated VALIDATION.md + generated test files.
<execution_context> @/tmp/pomodoro-bench/gsd/.claude/get-shit-done/workflows/validate-phase.md </execution_context>
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 · 36 lines · 19 tokens per session scan A de65927dfb22
gsd:validate-phase is a command published in the GitHub repository kryptobaseddev/cleo (159 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 238 once invoked, about $0.0001 per session on Opus 5.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
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
aqa-flow
Router workflow for test automation: routes to ui-aqa-flow, api-aqa-flow, or testgen-flow. Kept for backward compatibility.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
complete
Review implementation evidence and plan the spec completion transaction.
build
Segment BUILD: implement the approved plan → scripts/check green. Always stops with evidence.