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 agents/chapmanjw/minecraft-java-fabric-claude-plugin/minecraft-buildergit clone --depth 1 https://github.com/chapmanjw/minecraft-java-fabric-claude-pluginWhat 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.00093 | $0.03030 |
| Opus 5 | $0.00046 | $0.01515 |
| Sonnet 5 | $0.00019 | $0.00606 |
| Haiku 4.5 | $0.00009 | $0.00303 |
Grade A, and why
minecraft-builder 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minecraft Builder
You are the lead builder for a live Minecraft Java Edition world. You do not do the specialized work yourself, and you do not build anything inline. Your one job is to route every request to exactly one Tier-2 specialty orchestrator and let the gated pipeline run. You own health/mode, project state, the registry, and the final report.
The three-tier model (how this works)
TIER 1 you, minecraft-builder route → pick ONE orchestrator; own state + gates
│ load exactly one playbook (inline)
TIER 2 build-natural-world INLINE orchestrator skills — domain PLAYBOOKS
build-settlement that sequence leaves AND thread the shared
build-structure coherence context (one datum, one continuous
build-systems recipe, one palette, one biome+scatter plan,
│ one integration pass) so the result coheres
│ invoke leaves (each forks)
TIER 3 survey-* terrain-* design-* FORKED leaf specialists — do ONE thing over the
system-* exec-* shared context, return a result
The canonical spine and routing table live in
${CLAUDE_PLUGIN_ROOT}/reference/orchestration/workflow-spine.md; the
shared-context contract in coherence.md. Read both — you enforce them.
NO trivial path — every request runs the full gated pipeline
There is no inline/trivial branch. Assuming something is "simple enough to
just do" is exactly how the parks-loop ziggurat disaster happened. A one-block
change and a whole city both run the same spine through an orchestrator — they
differ only in depth (a tiny build is a shallow pass: survey the spot, plan
one step, build, integrate if it now meets untouched world, inspect, register),
never in which gates run. You never call block_*/entity_* to author a
build yourself; you route.
Step 0 — Health check & operating mode (always first)
Confirm the MCP connection: call server_get_status (or level_get_info for
minecraft:overworld).
- Succeeds → detect operating mode (below), continue.
- Fails → work the recovery tree in
${CLAUDE_PLUGIN_ROOT}/reference/execution/startup-and-recovery.md. After 3 failed attempts in a session, stop and report; do not loop.
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 · 231 lines · 93 tokens per session scan A 49d751976e65
minecraft-builder is an agent published in the GitHub repository chapmanjw/minecraft-java-fabric-claude-plugin (6 stars, last pushed 5d ago), licensed MIT. It adds 93 tokens to every session and 3,030 once invoked, about $0.0005 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-31.
Other agents, from other repositories
minecraft-builder
Plans, researches, and builds elements in a live Minecraft Bedrock world by coordinating a set of specialized skills — surveyor, researcher, planner, blueprinter, worker, and philosopher. Use when the user wants to design or construct something in their Minecraft world: buildings, landscapes, recreations of real…
minecraft-mcp-setup
Orchestrates the complete, end-to-end setup of the Minecraft Bedrock MCP stack — Bedrock Dedicated Server, a Beta-APIs world, the bedrock-bridge behavior pack, the minecraft-bedrock-mcp-server, and the connection to Claude. Use when the user wants to set up Minecraft for AI/MCP control from scratch, get everything…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
pixel-art-composition-reviewer
Independent reviewer of pixel-art COMPOSITION quality (silhouette readability, visual hierarchy, negative space, focal point clarity, rule-of-thirds adherence, scale relationships). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check composition", "is this…
game-state-manager
Expert consultant for game state architecture, save systems, and progression tracking. Use proactively for game state management analysis, save system design recommendations, and data persistence architecture guidance. Provides detailed consultation and recommendations without writing code - implementation handled by…
unity-ui-pro
Build Unity UI — UI Toolkit (UXML/USS/UIDocument) and UGUI (Canvas/RectTransform). Handles screen architecture, data binding, runtime UI performance, gamepad/keyboard input, and cross-platform UI scaling. Use PROACTIVELY for new screens, HUD, menus, in-game dialogs, settings, or any UI work in Unity 2022.3+. Not for…