update

A command for checking whether a newer version of CoalTipple is available and choosing how future update checks are handled.

In plain words
What is it for?
Use it to select automatic checks, reminders, or no checks, and to start a manual update procedure.
Why use it?
It gives you control over update reminders and avoids unexpected configuration changes or repeated checks.

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/coaltipple/update
Clone the repo
git clone --depth 1 https://github.com/TheColliery/CoalTipple
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 550 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00026 $0.00550
Opus 5 $0.00013 $0.00275
Sonnet 5 $0.00005 $0.00110
Haiku 4.5 $0.00003 $0.00055

Measured 2d ago against content hash 038ee7c1d6bb, 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.

Origin

This is a copy

88% identical to update — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/update.md · 26 lines

What it actually says

CoalTipple keeps itself current through the conductor (session start), gated by .coaltipple.json updateMode (ask | auto | remind | off, default ask) and throttled to once per updateCheckDays (default 14). Self-update is independent of routing (enableRouting / mode) — its own off-switch is updateMode: off. This command is the agent procedure each mode triggers — and a manual entry point. Always answer in the user's language; offer choices via your question tool; never spend tokens or change config without a chosen option.

ask — present the 3-way choice via your question tool:

  • auto — the agent web-checks on a ~updateCheckDays cadence and offers updates (~1-2K tokens/check).
  • remind — a free periodic reminder; the user runs the update themselves.
  • off — no reminders.

Save the pick (no forced check — the chosen mode drives future sessions): node scripts/configure.mjs --updateMode <auto|remind|off> (run from the CoalTipple repo, or wherever .coaltipple.json lives).

auto (the version CHECK — the only token spend, standing-consented):

  1. Get the latest published tag (graceful — never assume git/network is present): git ls-remote --tags --sort=-v:refname https://github.com/TheColliery/CoalTipple.git | head -1 (parse the trailing vX.Y.Z; ignore ^{} deref lines).
  2. Compare to the installed version in .claude-plugin/plugin.json (the plugin cache copy, or the repo copy if working from source).
  3. If a newer tag exists → OFFER (don't auto-run): claude plugin update coaltipple@coaltipple then /reload-plugins. If current → "up to date."
  4. Graceful fallback (no-external-assumption): if git ls-remote fails, git is missing, or there is no network, say "Can't check for updates offline — update manually with claude plugin update coaltipple@coaltipple when you're back online" and stop. Never crash, never assume a version.

remind — nothing for the agent to do; the conductor already surfaced the free reminder line. (If invoked manually, run the auto check above on request.)

off — no update activity.

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 · 26 lines · 26 tokens per session scan A 038ee7c1d6bb

Subscribe to this mod's changes

update is a command published in the GitHub repository TheColliery/CoalTipple (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 550 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to update, differing in 14 lines, and is treated as a copy.