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.
git clone --depth 1 https://github.com/alphabravo-oss/guildWrote 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/plugins/alphabravo-oss/guild/foundry)<a href="https://agentmods.dev/plugins/alphabravo-oss/guild/foundry"><img src="https://agentmods.dev/badge/plugins/alphabravo-oss/guild/foundry/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/plugins/alphabravo-oss/guild/foundry"><img src="https://agentmods.dev/badge/plugins/alphabravo-oss/guild/foundry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
foundry 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 13d 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
{
"name": "foundry",
"description": "Autonomous build-verify-fix loop for Claude Code. Reads a Forge spec, decomposes it into castings with pre-authored teammate prompts, validates through an 11-dimension F0.9 gate (including F0.7 intent-carrier coverage), builds in parallel waves with server-side evidence re-execution and per-requirement-ID binding, runs up to 8 verification streams (TRACE, FLOW_TRACE, PROVE, RESEARCH_AUDIT, COVERAGE_DIFF, SIGHT, TEST/PROBE, TEST_OBSERVATIONS), grinds defects to zero, then assays with fresh eyes. Brownfield runs consume a flow delta; greenfield and cosmetic runs use the end-state pipeline. Forge plans. Foundry builds.",
"version": "4.11.2",
"author": {
"name": "AlphaBravo"
},
"userConfig": {
"model": {
"type": "string",
"title": "Agent model",
"description": "Model for this plugin's config-steerable agents. Accepted values: opus, sonnet, haiku, fable, inherit. Leave unset to change nothing — each agent's own model pin governs.",
"required": false
}
},
"mcpServers": {
"foundry": {
"command": "uv",
"args": [
"run",
"--project",
"${CLAUDE_PLUGIN_ROOT}/mcp-server",
"foundry-mcp",
"--project-root",
"${CLAUDE_PROJECT_DIR}"
],
"env": {
"FOUNDRY_MODEL": "${user_config.model}"
}
}
}
}
What it installs
The manifest is a name and a version. 4 skills, 4 commands, 12 agents travel with it, and installing the plugin installs all of them — 1,007 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill sight A 58 tokens
- Skill prove A 60 tokens
- Skill temper A 55 tokens
- Skill trace A 40 tokens
- Command start A 10 tokens
- Command update A 10 tokens
- Command setup A 8 tokens
- Command stop A 8 tokens
- Agent flow-tracer A 57 tokens
- Agent tracer A 26 tokens
- Agent coverage-diff A 49 tokens
- Agent research-auditor A 52 tokens
- Agent spec-test-deriver A 85 tokens
- Agent flow-mapper A 74 tokens
- Agent intent-carrier A 75 tokens
- Agent pattern-mapper A 81 tokens
- Agent codebase-mapper A 81 tokens
- Agent nyquist-auditor A 41 tokens
- Agent research-synthesizer A 61 tokens
- Agent test-observations-adjudicator A 76 tokens
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.
- 13d ago Changed 396b779d0499
- 21d ago Changed 9b6c1aea5897
- 1mo ago Changed 8dd409a2c7de
- 1mo ago Changed 010f74d51ede
- 1mo ago Changed 6a442f7571e3
- 1mo ago First seen · 33 lines scan A d60413d34b7e
foundry is a plugin published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.