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/chrisblattman/claudeblattmanWrote 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/chrisblattman/claudeblattman/grok)<a href="https://agentmods.dev/commands/chrisblattman/claudeblattman/grok"><img src="https://agentmods.dev/badge/commands/chrisblattman/claudeblattman/grok/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/chrisblattman/claudeblattman/grok"><img src="https://agentmods.dev/badge/commands/chrisblattman/claudeblattman/grok.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.00015 | $0.00064 |
| Opus 5.5 | $0.00006 | $0.00026 |
| Sonnet 5.5 | $0.00003 | $0.00013 |
| Haiku 4.5 | $0.00002 | $0.00006 |
Grade A, and why
grok 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 2d 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
Follow the installed Ask Agents skill, selecting grok exactly. Use its shared runner and subscription checks, then read the returned report. No browser automation or API fallback. Missing connections return an explicit error and setup guidance.
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.
- 2d ago First seen · 6 lines · 15 tokens per session scan A 6a44230d4024
grok is a command published in the GitHub repository chrisblattman/claudeblattman (474 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 64 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-10-30.
Other commands, from other repositories
statusbar-style
Switch the status-bar look (aurora blocks / aurora thin / classic).
statusbar-preview
Render the three status-bar looks using your real cached data.
statusbar-reset
Wipe the status-bar config back to defaults.
context-stats
Display context window usage and token statistics.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
help
Explain Ralph Wiggum technique and available commands.