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 instructions/simonerecchia/minecraft-schematic-lab/claude-mdgit clone --depth 1 https://github.com/SimoneRecchia/minecraft-schematic-labWrote 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/instructions/simonerecchia/minecraft-schematic-lab/claude-md)<a href="https://agentmods.dev/instructions/simonerecchia/minecraft-schematic-lab/claude-md"><img src="https://agentmods.dev/badge/instructions/simonerecchia/minecraft-schematic-lab/claude-md.svg" alt="Measured on agentmods" 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 | $0.03558 | $0.03558 |
| Opus 5 | $0.01779 | $0.01779 |
| Sonnet 5 | $0.00712 | $0.00712 |
| Haiku 4.5 | $0.00356 | $0.00356 |
Grade D, and why
minecraft-schematic-lab CLAUDE.md scanned grade D with 3 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
`curl -s -X POST http://127.0.0.1:8765/api/session/build -H 'content-type: application/json' -d '<BuildSpec JSON>'`. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
4. Never use `sudo`. Never `rm -rf node_modules` or `dist`. If a network step fails (offline), tell the Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. Make sure the server is running on 8765. Check `curl -s http://127.0.0.1:8765/api/health` (it How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
minecraft-schematic-lab — operating protocol for Claude Code
You are operating inside minecraft-schematic-lab. Read this file as your instructions for this project. The end user is a Minecraft player, not a programmer — they will just say things like "build me a fantasy castle" or "make the roof brick". Your job is to make that work, including doing the one-time technical setup yourself, in plain language, the first time.
What this project is
A fully-local pnpm/TypeScript monorepo (Node 22+, ESM). One Node process, on port 8765, serves
three things at once: the HTTP API, a minimal browser viewer (3D preview + Export button), and the
MCP stdio server. You compile a BuildSpec (JSON) into a WorldEdit Sponge .schem and show
it live in the browser. Nothing leaves the machine — no cloud, no account, no database. The server is
run through tsx at runtime (it is not compiled); the only build artifact that matters is the web
viewer at apps/web/dist.
The repo root is the directory that contains this file. Throughout, <REPO> = that absolute path.
The golden rule: check setup state FIRST on any build/modify request
When the user asks you to build, change, render, export, or version a schematic, before anything else determine whether the project is set up. "Set up" means all of these are true:
noderesolves and its major version is >= 22 (node -p 'process.versions.node.split(".")[0]').pnpmresolves.<REPO>/node_modulesexists.<REPO>/apps/web/dist/index.htmlexists (the built viewer). NOTE:dist/is git-ignored, so a fresh checkout never has it — the build step below must run at least once.- The MCP connector
minecraft-schematic-labis registered (only relevant for subsequent builds — see "MCP not live yet" below; the first build does not need it).
If any of 1–4 is missing, the project is not set up. Do this, in order:
- Explain to the user, in plain language (match their language — they often write Italian), e.g.: "This is the first time you're building something, so I need to set up the tool once. It will take a minute: I'll install what's needed locally (no admin password required) and then build your schematic. After this it just works." Do not dump technical jargon on them.
- Run the setup helper:
bash <REPO>/scripts/setup.sh. It is idempotent and safe to re-run; it installs Node via nvm if missing (no sudo), enables pnpm via corepack, runspnpm install+pnpm build, and — if theclaudeCLI is available — registers the MCP connector using a PATH-safe wrapper. Read its output: it prints clear progress and, at the end, a summary plus any manual command you still need to run (e.g. connector registration ifclaudeisn't on PATH). - If
scripts/setup.shis missing for some reason, perform the equivalent steps yourself: detect/install Node 22+ via nvm without sudo,corepack enable pnpm && corepack prepare [email protected] --activate,pnpm --dir <REPO> install,pnpm --dir <REPO> build. - Never use
sudo. Neverrm -rf node_modulesordist. If a network step fails (offline), tell the user plainly that the first-time setup needs internet, then stop.
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.
- 4d ago First seen · 209 lines · 3,558 tokens per session scan D c7541cead8b0
minecraft-schematic-lab CLAUDE.md is an instructions file published in the GitHub repository SimoneRecchia/minecraft-schematic-lab (3 stars, last pushed yesterday), licensed MIT. It adds 3,558 tokens to every session, about $0.0178 per session on Opus 5. A static security scan graded it D with 3 findings (sends data to an external url, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
minecraft_mcp AGENTS.md
AGENTS.md instructions for rodcordeiro/minecraft_mcp, covering minemcp, como usar este contexto, regras rápidas and skills condicionais.
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Copilot instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.