update

A command for checking whether a newer CoalWash version is available and deciding how update checks should be handled. CoalWash is a tool that cleans and protects an AI agent’s stored memory.

In plain words
What is it for?
Use it to check the installed CoalWash version, offer a manual update, and configure update checks as ask, automatic, reminder-based, or off.
Why use it?
It makes version checking explicit and keeps updates from being applied automatically without consent. It also accounts for cases where network access or Git is unavailable.

Command

Install

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.

agentmods
npx agentmods add commands/thecolliery/coalwash/update
Clone the repo
git clone --depth 1 https://github.com/TheColliery/CoalWash
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00279
Opus 5 $0.00012 $0.00139
Sonnet 5 $0.00005 $0.00056
Haiku 4.5 $0.00002 $0.00028

Measured 2d ago against content hash a17e7f7b5fad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update 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.

commands/update.md · 12 lines

What it actually says

Kind-1 self-update — the agent verifies (online), the hook only schedules (it never networks). If git/network is unavailable, say so and suggest updating manually later (never assume either exists).

  1. Check. Web-check the latest published CoalWash tag (any means available — the GitHub releases/tags page or API) vs the installed version in .claude-plugin/plugin.json.
  2. Offer (consent-gated — the only token spend). Newer available → OFFER claude plugin update coalwash@coalwash (then restart); on a file-copy install, offer to re-copy the updated files instead. Already current → say so in one line.
  3. Cadence. To change how updates are handled, set updateMode (ask | auto | remind | off) and updateCheckDays in .coalwash.json. auto lets this check run when due without re-asking; off silences it entirely.

Security note: CoalWash mutates memory — fidelity/safety fixes matter more than cosmetics here; still, this never auto-applies. It offers, the user runs the update.

Changes

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.

  1. 2d ago First seen · 12 lines · 23 tokens per session scan A a17e7f7b5fad

Subscribe to this mod's changes

update is a command published in the GitHub repository TheColliery/CoalWash (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 23 tokens to every session and 279 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-30.