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.
npx agentmods add commands/lucasduys/forge/updategit clone --depth 1 https://github.com/LucasDuys/forgeWhat 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 | $0.00006 | $0.01041 |
| Opus 5 | $0.00003 | $0.00521 |
| Sonnet 5 | $0.00001 | $0.00208 |
| Haiku 4.5 | $0.00001 | $0.00104 |
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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Update
Pull the latest Forge from upstream. Detects how the plugin is installed (git checkout vs marketplace cache vs custom --plugin-dir), runs the appropriate update mechanism, and reports the version delta. Safe to run repeatedly.
What it does
The command shells out to scripts/forge-update.cjs which:
- Locates the plugin install — uses
$CLAUDE_PLUGIN_ROOTif set, otherwise walks up from the script directory looking for.claude-plugin/plugin.json. Override with--plugin-root PATH. - Reads the current version from
.claude-plugin/plugin.json. - Detects the install method:
- git checkout (
.git/present) — fetches origin, fast-forwards the current branch, refuses if the working tree is dirty unless--forceis given - marketplace cache (path contains
plugins/cache/) — prints the manualclaude plugin marketplace updateinstructions and exits with code 2 (those steps must be run from the user's terminal, not from inside Claude Code) - unknown — prints diagnostics and exits with code 2
- git checkout (
- Runs the update (or just shows what would change if
--checkis passed). - Reports the version delta and prompts the user to run
/reload-plugins.
Pre-flight Check
Run the script with --check first to see what would change before applying:
node "${CLAUDE_PLUGIN_ROOT}/scripts/forge-update.cjs" --check
If updates are available, ask the user whether to proceed. If they say yes, run without --check.
If the user passed --check themselves, stop after the check report and tell them to re-run without --check when ready.
Parse Arguments
Parse flags from $ARGUMENTS:
| Flag | Default | Description |
|---|---|---|
--check |
off | Report only — show incoming commits, do not modify the working tree |
--force |
off | Stash uncommitted local changes before pulling (and pop them after) |
--plugin-root PATH |
auto | Override automatic plugin install discovery |
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.
- 2d ago First seen · 95 lines · 6 tokens per session scan A 82d2d938ec80
update is a command published in the GitHub repository LucasDuys/forge (55 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 1,041 once invoked, about $0.0000 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.
Other commands, from other repositories
audit-system
Run a comprehensive audit of an existing design system for consistency, completeness, and accessibility.
build-presentation
Build a design presentation end to end — audience framing, narrative structure, and supporting rationale.
discover
Run a full user research cycle — persona creation, empathy mapping, and journey mapping for a product or feature.
interview
Prepare an interview script or summarize an interview transcript into structured insights.
deploy
Deploy the application to production.
eg-new-feature
Build a new feature using the elephant/goldfish workflow — design doc, goldfish design check, implement, review, validate.