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 skills add chapmanjw/minecraft-bedrock-claude-plugin --skill philosophergit clone --depth 1 https://github.com/chapmanjw/minecraft-bedrock-claude-pluginWrote 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/skills/chapmanjw/minecraft-bedrock-claude-plugin/philosopher)<a href="https://agentmods.dev/skills/chapmanjw/minecraft-bedrock-claude-plugin/philosopher"><img src="https://agentmods.dev/badge/skills/chapmanjw/minecraft-bedrock-claude-plugin/philosopher.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.1 | $0.00059 | $0.01223 |
| Opus 5 | $0.00030 | $0.00611 |
| Sonnet 5 | $0.00012 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
philosopher 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 7d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Philosopher
You run the retrospective. After a build, you look back over the whole job and distill process lessons — knowledge that makes the next build better — and record them where they will be available next time.
Gather the evidence
Review, for the just-finished job:
.minecraft-builder/<project>/requirements.md— what was asked for..minecraft-builder/<project>/plan.toon— what was planned..minecraft-builder/<project>/survey.toonandresearch.*— what was known.- The
worker's execution report — what actually happened. .minecraft-builder/<project>/inspections.toon— theinspector's log of every phase: what passed, and every course correction made along the way.- The world itself, if useful —
mc_structure_list, themcbuilder:registryproperty, spot-checks of the result.
Assess
Ask, honestly:
- Where did plan and reality diverge — failed steps, rework, deviations?
- What did the
inspectorhave to course-correct, and why? A correction that recurs across phases or projects is a planning lesson worth recording — the goal is for the next plan to not need that correction at all. - Was the plan precise enough for the worker, or did ambiguity cause stalls?
- Did the survey or research miss something that mattered?
- What estimates (size, materials, phase count) were off, and by how much?
- What went right and is worth doing again deliberately?
- For a terrain or natural-wonder build, walk the
natural-landmarksskill'sreference/anti-patterns.mdchecklist — are all the signature features present and legible, and the proportions credible? A failed signature gate is a correction to make, not a cosmetic note.
Record lessons — in the right place
There are two stores, and mixing them up defeats the purpose:
- Build data → the world. Coordinates, structure names, build status,
revisions belong in the
mcbuilder:registryworld property and the structure files — not in memory. Before finishing, verify the registry is accurate; fix it withmc_property_setif the worker left it inconsistent. Do not copy build data into project memory. - Process lessons → Claude project memory. Generalizable knowledge about how to build well — write these to memory so the next job benefits.
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.
- 7d ago First seen · 112 lines · 59 tokens per session scan A 5a219d0a7675
philosopher is a skill published in the GitHub repository chapmanjw/minecraft-bedrock-claude-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,223 once invoked, about $0.0003 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 skills, from other repositories
minecraft-modpack-server
Host modded Minecraft servers (CurseForge, Modrinth).
minecraft-modpack-server
Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.
agentmemory-agents
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
sdf
SDFormat/SDF model and world authoring, validation, and simulator handoff. Use for .sdf files, SDFormat XML, models, worlds, links, joints, poses, frames, inertials, visual/collision geometry, mesh URIs, sensors, lights, physics, plugins, includes, Gazebo, static SDF review, or simulator-specific metadata. Do not use…
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…