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/khur/clawdbod/historygit clone --depth 1 https://github.com/khur/clawdbodWrote 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/khur/clawdbod/history)<a href="https://agentmods.dev/commands/khur/clawdbod/history"><img src="https://agentmods.dev/badge/commands/khur/clawdbod/history.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.00013 | $0.00154 |
| Opus 5 | $0.00006 | $0.00077 |
| Sonnet 5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
history 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 today.
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
ClawdBod History
- Pick a limit: default 20; a number in
$ARGUMENTS→ that number (max 100); "all" → 100. - Run with the Bash tool:
node "${CLAUDE_PLUGIN_ROOT}/scripts/stats.mjs" --limit LIMIT - Print the output verbatim inside a code block. Add nothing else unless the user asks a follow-up.
The script already handles the empty-log case, totals over the whole log, newest-first ordering, and the "Showing last N of M" note.
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.
- today Changed · -35 lines scan B → A d42924c5a5aa
- 4d ago First seen · 51 lines · 13 tokens per session scan B 9fe819933e48
history is a command published in the GitHub repository khur/clawdbod (5 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 154 once invoked, about $0.0001 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
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
history
List past OCR review sessions.
new-sdk-app
Create and setup a new Claude Agent SDK application.
audit-project-github
This file contains GitHub integration for /audit-project.
claudikins-kernel:verify
Post-execution verification gate. Tests, lint, type-check, then see it working.