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.
/plugin marketplace add alphabravo-oss/guild/plugin install foundryWrote 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.
[](https://agentmods.dev/commands/alphabravo-oss/guild/update)<a href="https://agentmods.dev/commands/alphabravo-oss/guild/update"><img src="https://agentmods.dev/badge/commands/alphabravo-oss/guild/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.
<a href="https://agentmods.dev/commands/alphabravo-oss/guild/update"><img src="https://agentmods.dev/badge/commands/alphabravo-oss/guild/update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00283 |
| Opus 5.5 | $0.00004 | $0.00113 |
| Sonnet 5.5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
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 1mo 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.
What it actually says
Foundry Update Command
Upgrade the foundry MCP server to the latest published code. Does not reinstall
prerequisites, does not touch .mcp.json, does not restart anything else — use
/foundry:setup for a first-time install.
Run the update:
"${CLAUDE_PLUGIN_ROOT}/scripts/update-mcp.sh" $ARGUMENTS
After the script completes:
- If the version changed, tell the user to restart Claude Code to load the new server.
- If it reports "Already up to date", say so and stop — no restart needed.
- If it failed, surface the traceback verbatim. A rebuild that cannot start is almost always a dependency that resolved to an incompatible major version, not a problem with the user's setup.
Why this command exists: the MCP entry points uvx at an unpinned git URL, and uvx caches the git build by resolved commit — it does not re-resolve on later runs. Without an explicit refresh the same commit is served indefinitely. This command is that refresh.
Forge plans. Foundry builds.
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.
- 1mo ago First seen · 34 lines · 10 tokens per session scan A be758c97f61f
update is a command published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 11d ago), licensed MIT. It adds 10 tokens to every session and 283 once invoked, about $0.0000 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-04.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.