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/statusgit 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/status)<a href="https://agentmods.dev/commands/001tmf/blatant-why/status"><img src="https://agentmods.dev/badge/commands/001tmf/blatant-why/status.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.00004 | $0.00089 |
| Opus 5 | $0.00002 | $0.00044 |
| Sonnet 5 | $0.00001 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
status 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
Show the current status of all active and recent design campaigns.
For each campaign, display:
- Run ID and tool used
- Current pipeline stage
- Design progress (completed/total)
- Top scores so far (ipTM, ipSAE)
- Any warnings or issues
- Elapsed time
If no campaigns are active, suggest starting one with the appropriate tool for the current mode.
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 · 16 lines · 4 tokens per session scan A a65f6856d089
status is a command published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 18d ago), licensed MIT. It adds 4 tokens to every session and 89 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
graphiti-health
Display unified real-time health status for Neo4j Aura and Graphiti services.
scaffold-fastmcp-v2
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-aura-stats
Generate production graph statistics for Neo4j Aura analytics and capacity planning.
scaffold-fastmcp
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-docker-stats
Generate development environment statistics for Docker Neo4j namespace management.
graphiti-verify
Run Day 1 verification sequence to confirm environment is working.