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/test.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/test)<a href="https://agentmods.dev/commands/mylee04/who-ran-what/test"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/test/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/test"><img src="https://agentmods.dev/badge/commands/mylee04/who-ran-what/test.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.00009 | $0.00296 |
| Opus 5.5 | $0.00004 | $0.00118 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
test 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.
What it actually says
Run Tests
What This Command Does
- Runs all test scripts in the tests/ directory
- Validates command output
- Reports pass/fail status
Process
1. Check Test Directory
# Verify tests directory exists
if [[ ! -d "tests" ]]; then
echo "No tests directory found"
exit 0
fi
2. Run Tests
# Run each test file
for test_file in tests/*.sh; do
echo "Running: $test_file"
bash "$test_file"
done
3. Quick Smoke Tests
If no test directory exists, run these basic checks:
# Test help command
./bin/who-ran-what help
# Test version command
./bin/who-ran-what version
# Test default dashboard
./bin/who-ran-what
# Test each subcommand
./bin/who-ran-what today
./bin/who-ran-what week
./bin/who-ran-what month
./bin/who-ran-what agents
./bin/who-ran-what projects
Success Criteria
- All commands exit with code 0
- No error messages in stderr
- Output is readable and formatted correctly
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 · 62 lines · 9 tokens per session scan A 942ebd7e361b
test is a command published in the GitHub repository mylee04/who-ran-what (3 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 296 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
complete
Review implementation evidence and plan the spec completion transaction.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-bar
Generate a floating QA test overlay for the current branch's UI changes. Use when user says /test-bar, needs visual QA scenarios, or wants to test conditional rendering paths.
write-skill-test
RED-GREEN-REFACTOR implementation for writing-skills: Baseline testing, minimal skill writing, loophole closure, and full creation checklist.
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.