Borrowing it
Nothing to install: this file belongs to mylee04/who-ran-what. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mylee04/who-ran-what/main/.claude/commands/validate.mdgit clone --depth 1 https://github.com/mylee04/who-ran-whatWrote 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/mylee04/who-ran-what/validate)<a href="https://agentmods.dev/commands/mylee04/who-ran-what/validate"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/validate/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/mylee04/who-ran-what/validate"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/validate.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.00007 | $0.00170 |
| Opus 5 | $0.00003 | $0.00085 |
| Sonnet 5 | $0.00001 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
validate 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 9d 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
Validate Scripts
Execute these steps NOW:
Step 1: Run shellcheck on all scripts
shellcheck -x -e SC1091 bin/who-ran-what
shellcheck -x -e SC1091 lib/who-ran-what/**/*.sh
shellcheck -x -e SC1091 tests/*.sh
Step 2: Run syntax check
bash -n bin/who-ran-what
Step 3: Run tests
./tests/run_all.sh
Step 4: Report results
Tell the user:
- ✅ How many files passed
- ❌ Any errors found (with line numbers)
- 💡 Suggested fixes for any issues
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.
- 9d ago First seen · 35 lines · 7 tokens per session scan A 7f1f03a7773c
validate is a command published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 170 once invoked, about $0.0000 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
run-manual-validation.en
Run host-side task validation and record sanitized evidence.
test-integration.en
Run the integration test workflow.
test.en
Run the full project test workflow.
feature-implement-execute
Phase 4 of develop: Execute the implementation plan with per-task TDD, quality gates, and completion verification.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
audit-mirage-analyze
Phases 2-3 and 7 of auditing-green-mirage: systematic line-by-line audit, the Green Mirage Patterns, named assertion shapes, and the fix-verification Test Adversary prompt.