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/crucible)<a href="https://agentmods.dev/plugins/alphabravo-oss/guild/crucible"><img src="https://agentmods.dev/badge/plugins/alphabravo-oss/guild/crucible/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/crucible"><img src="https://agentmods.dev/badge/plugins/alphabravo-oss/guild/crucible.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
crucible 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
{
"name": "crucible",
"description": "A mini-foundry — the build-verify-fix engine without the MCP server or the planning interview. You bring a structured spec (requirement IDs + acceptance criteria); crucible builds it and refuses to let it drift. /crucible:build <spec-file> decomposes the spec into units with DISJOINT file ownership, shows you the split for one approval, then runs a Workflow engine: CAST (parallel deliberate-engineering builders, each handed its unit prompt verbatim, each producing re-executable evidence bound to requirement IDs) -> INSPECT (blind orthogonal verification streams — wiring exists/substantive/wired, spec-before-code assay, and server-side re-execution of every evidence command) -> GRIND (every non-passing verdict is a defect; fix and full-re-inspect, loop until zero or a cycle cap) -> ASSAY (fresh-eyes agents read the spec first, form expectations, then confirm each requirement). Refuses a dirty tree; edits the shared working tree under disjoint ownership; commits per-unit only on your say-so so any unit is one revert away. Drops what needs the heavy machinery: no MCP gates/hashing, no isolated-worktree evidence, no brownfield flow-graph interview. Keeps the load-bearing principles: the engine routes and verifies, it never re-narrates the spec or judges the code itself.",
"version": "0.1.0",
"author": {
"name": "AlphaBravo"
}
}
What it installs
The manifest is a name and a version. 1 command, 2 agents travel with it, and installing the plugin installs all of them — 206 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 9 lines scan A cc432e681fff
crucible 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
load-tester
Load and stress testing for APIs and web services.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.
pict-test-designer
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected…
local-test-plugin
Symlink-based local plugin testing for development workflow.
claude-md-management
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.