update

update is a command for Claude Code from nxtg-ai/forge-plugin. It costs 14 tokens per session (1,222 once invoked), scanned D, original, MIT.

An update command for the Forge plugin and its project configuration. It detects the installation, fetches newer plugin content, handles a known stale marketplace-cache problem, and checks configuration validity, schema migration, and hooks.

In plain words
What is it for?
Use it to check for updates, update the plugin, repair a failed update, reinstall when necessary, and verify the project’s governance configuration and hooks.
Why use it?
It addresses cases where an update appears to run but the local plugin copy remains old. It also helps reveal whether the project configuration needs updating.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions Claude Code.

Part of the nxtg-forge plugin — 27 skills, 24 commands, 33 agents shipped together

Good fit Use it to check for updates, update the plugin, repair a failed update, reinstall when necessary, and verify the project’s governance configuration and hooks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/nxtg-ai/forge-plugin/update
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.

Clone the repo
git clone --depth 1 https://github.com/nxtg-ai/forge-plugin

Made for: Claude Code.

Or install nxtg-forge, the plugin that ships this one along with the rest of its 27 skills, 24 commands, 33 agents.

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/nxtg-ai/forge-plugin/update/github.svg)](https://agentmods.dev/commands/nxtg-ai/forge-plugin/update)
Your own site
<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/update"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/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/nxtg-ai/forge-plugin/update"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,222 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 2 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.00014 $0.01222
Opus 5.5 $0.00006 $0.00489
Sonnet 5.5 $0.00003 $0.00244
Haiku 4.5 $0.00001 $0.00122

Measured 12d ago against content hash b6c733b1f9ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade D, and why

update scanned grade D with 2 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 12d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

echo "=== installed_plugins.json ===" && cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); [print(f'{k}: {[s.get(\"scope\",\"?\") for s in v]}') for k,v in d.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf ~/.claude/plugins/marketplaces/*forge*
plugins/nxtg-forge/commands/update.md · 131 lines

How it starts

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

Forge Update

You are the Update Agent — pull the latest Forge plugin and refresh project config. Includes a built-in workaround for Claude Code #29071 (stale marketplace cache).

Parse Arguments

Arguments received: $ARGUMENTS

Options:

  • No arguments: Check for updates, update plugin, refresh project config
  • --check: Only check what would be updated (no changes)
  • --plugin: Only update the plugin itself
  • --config: Only update governance config and hooks

Step 1: Detect Current Install

The plugin may be registered under different names (forge, forge@forge, etc.) and scopes (local, user). Run:

echo "=== installed_plugins.json ===" && cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); [print(f'{k}: {[s.get(\"scope\",\"?\") for s in v]}') for k,v in d.get('plugins',{}).items() if 'forge' in k.lower()]" 2>/dev/null || echo "no installed_plugins.json"
echo "=== marketplace dir ===" && ls -d ~/.claude/plugins/marketplaces/*forge* 2>/dev/null || echo "no marketplace clone"
echo "=== plugin.json version ===" && cat ~/.claude/plugins/marketplaces/*forge*/.claude-plugin/plugin.json 2>/dev/null | python3 -c "import sys,json; print(json.load(sys.stdin).get('version','?'))" 2>/dev/null || echo "unknown"

Display:

## Forge Update

**Installed:** {plugin identifier} ({scope})
**Marketplace version:** {version from marketplace clone}

Step 2: Sync Marketplace (#29071 bypass)

Claude Code's plugin update fetches but never merges the marketplace clone. We pull it ourselves first.

MARKETPLACE_DIR=$(find ~/.claude/plugins/marketplaces/ -maxdepth 1 -name "*forge*" -type d 2>/dev/null | head -1)
if [ -n "$MARKETPLACE_DIR" ]; then
  cd "$MARKETPLACE_DIR" && git pull --ff-only origin main 2>&1 || git pull --ff-only origin master 2>&1
  NEW_VERSION=$(python3 -c "import json; print(json.load(open('.claude-plugin/plugin.json')).get('version','?'))" 2>/dev/null)
  echo "SYNCED: $MARKETPLACE_DIR → v$NEW_VERSION"
else
  echo "NO_MARKETPLACE_CLONE"
fi

Read the full file on GitHub · 131 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. 12d ago Changed b6c733b1f9ab
  2. 1mo ago Changed · +9 lines · +14 tokens per session scan A → D 01b242dfa506
  3. 1mo ago First seen · 122 lines · 0 tokens per session scan A b591ff956757

Subscribe to this mod's changes

update is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 1,222 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.