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/001tmf/blatant-why/watchgit clone --depth 1 https://github.com/001TMF/blatant-whyWrote 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/001tmf/blatant-why/watch)<a href="https://agentmods.dev/commands/001tmf/blatant-why/watch"><img src="https://agentmods.dev/badge/commands/001tmf/blatant-why/watch.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.00008 | $0.00129 |
| Opus 5 | $0.00004 | $0.00064 |
| Sonnet 5 | $0.00002 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
watch 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 4d 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
Watch the live progress of design run $ARGUMENTS. Use the by-tools MCP server to check the current status and display the pipeline stages with progress indicators.
Show the pipeline progress display with:
- Current stage (marked with green dot ●)
- Completed stages (marked with ✓)
- Pending stages (marked with ○)
- Design count progress (X/Y designs)
- Elapsed time
Update every 30 seconds until complete. Report final results when done.
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.
- 4d ago First seen · 19 lines · 8 tokens per session scan A 1ddc29aafcaa
watch is a command published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 18d ago), licensed MIT. It adds 8 tokens to every session and 129 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-30.
Other commands, from other repositories
run-gpmolformer
Guide the user through running GP-MoLFormer on an AMD cluster via SLURM.
run-perf-hydragnn
Guide the user through performance engineering for HydraGNN Predictive GFM: one-shot perf-analysis (2-node training + TraceLens + Omnistat diagnosis) or iterative perf-optimizer-loop (accept/revert on epochtimes). This is not ensemble inference — use /run-hydragnn for that.
run-stormcast
Guide the user through running StormCast end-to-end on an AMD cluster via SLURM.
run-neuralgcm
Guide the user through running NeuralGCM end-to-end on an AMD cluster via Docker or SLURM.
run-gencast
Guide the user through running GenCast end-to-end on an AMD cluster.
run-swinunetr
Guide the user through training or inference with SwinUNETR on AMD GPUs.