update

update is a command for Claude Code from stellarshenson/claude-code-plugins. It costs 18 tokens per session (888 once invoked), scanned A, original, MIT.

A command for updating an existing document-processing output with corrections, new source material, or renewed verification. It first checks that its supporting toolkit is installed and current, then re-runs grounding checks on changed content.

In plain words
What is it for?
It helps revise processed documents, add sources, correct errors, and verify that changed content remains grounded in its sources.
Why use it?
It reduces the risk of publishing outdated or weakly supported document results. The version check prevents the command from running with an older toolkit than the installed plugin.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions .claude-plugin; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the document-processing plugin — 5 skills, 5 commands shipped together

Good fit It helps revise processed documents, add sources, correct errors, and verify that changed content remains grounded in its sources.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add stellarshenson/claude-code-plugins
Claude Code
/plugin install document-processing

Made for: Claude Code.

Or install document-processing, the plugin that ships this one along with the rest of its 5 skills, 5 commands.

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

agentmods badge for update

README.md
[![agentmods](https://agentmods.dev/badge/commands/stellarshenson/claude-code-plugins/update/github.svg)](https://agentmods.dev/commands/stellarshenson/claude-code-plugins/update)
Your own site
<a href="https://agentmods.dev/commands/stellarshenson/claude-code-plugins/update"><img src="https://agentmods.dev/badge/commands/stellarshenson/claude-code-plugins/update/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.

agentmods 80×15 button for update

Your own site · 80×15
<a href="https://agentmods.dev/commands/stellarshenson/claude-code-plugins/update"><img src="https://agentmods.dev/badge/commands/stellarshenson/claude-code-plugins/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 888 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00018 $0.00888
Opus 5.5 $0.00007 $0.00355
Sonnet 5.5 $0.00004 $0.00178
Haiku 4.5 $0.00002 $0.00089

Measured 21d ago against content hash ed8f7d1cd568, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 21d 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.

plugins/document-processing/commands/update.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Document Processing - Update

Read this plugin's skill file skills/update/SKILL.md and follow it. Updates existing 3-output/ document with new info, corrections, re-applied rules, or re-verification against updated sources - and always re-runs grounding CLI on changed content before declaring done (step 5 of skill is gate, not optional).

Toolchain gate (MANDATORY - run before anything else)

Run this first, every session, before any other work. The upgrade always runs; a version mismatch blocks.

python3 -m pip install --user --upgrade stellars-claude-code-plugins 2>&1 | tail -1
LIB=$(python3 -c "import importlib.metadata as m;print(m.version('stellars-claude-code-plugins'))" 2>/dev/null) || { echo "FATAL: toolkit unavailable"; exit 1; }
PLUG=$(grep -m1 '"version"' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null | cut -d'"' -f4)
OLDER=$(printf '%s\n%s\n' "$LIB" "$PLUG" | sort -V | head -1)
[ -n "$PLUG" ] && [ "$LIB" != "$PLUG" ] && [ "$OLDER" = "$LIB" ] && { echo "STALE: library $LIB older than plugin $PLUG - refusing to run on an outdated CLI; re-run the upgrade"; exit 1; }
echo "toolkit $LIB"

Run the CLI without touching the caller's project. The gate above puts it on PATH, so the bare command name is the whole invocation. uv run instead resolves whatever project the working directory sits in and writes uv.lock and .venv into it, so if you reach for uv pass --no-project (uv run --no-project <cli> ...) - it skips project discovery, leaves the tree untouched and still finds the same PATH binary. --no-sync and --frozen are not substitutes; both still create .venv.

Both branches exit non-zero and neither is advisory: an absent library (FATAL) and a version mismatch (STALE). A mismatch means the CLI is not the one this file was written against, so its documented flags and rules are unverified. Report the line and stop; do not work around it.

When to use

  • New source document added to 1-input/ - re-run affected sections
  • User found errors in 3-output/ document - correct and re-verify
  • Grounding audit failed - fix unconfirmed claims
  • Uniformization rules changed - re-apply to existing output
  • Additional context available - enrich existing document

Read the full file on GitHub · 48 lines

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. 21d ago Changed ed8f7d1cd568
  2. 1mo ago First seen · 48 lines · 18 tokens per session scan A e3fc5e9cef34

Subscribe to this mod's changes

update is a command published in the GitHub repository stellarshenson/claude-code-plugins (4 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 888 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-09-05.