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/asanderson/llm-redactWrote 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/asanderson/llm-redact/status)<a href="https://agentmods.dev/commands/asanderson/llm-redact/status"><img src="https://agentmods.dev/badge/commands/asanderson/llm-redact/status/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/asanderson/llm-redact/status"><img src="https://agentmods.dev/badge/commands/asanderson/llm-redact/status.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.00019 | $0.00804 |
| Opus 5.5 | $0.00008 | $0.00322 |
| Sonnet 5.5 | $0.00004 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00080 |
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 19d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 19d ago Changed · +2 lines 56e3562f09d2
- 1mo ago Changed e254bd01965d
- 1mo ago Changed · +5 lines ce7dbc3b8fc4
- 1mo ago First seen · 58 lines · 19 tokens per session scan A 6ef65a06fdae
status is a command published in the GitHub repository asanderson/llm-redact (7 stars, last pushed today), licensed AGPL-3.0. It adds 19 tokens to every session and 804 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-08-31.
Other commands, from other repositories
speckit.boundedrelay.execute-wave
Execute one dependency-safe routed wave through Claude Code and BoundedRelay.
speckit.boundedrelay.implementation-review
Run frozen Claude host and independent Codex implementation reviews.
speckit.boundedrelay.plan-review
Freeze Claude host findings before an independent BoundedRelay Codex plan review.
speckit.boundedrelay.route
Route approved tasks by estimated effort with a configurable provider target.
speckit.boundedrelay.handoff
Write an exact provider-aware continuation handoff.
tokendiet
Audit your code for wasteful LLM API spend and get a concrete plan to cut it — cache, batching, retry caps, prompt bloat. No fabricated numbers.