Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add chapmanjw/minecraft-java-fabric-claude-plugin/plugin install minecraft-javaWrote 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-java-fabric-claude-plugin/terrain-ecology)<a href="https://agentmods.dev/skills/chapmanjw/minecraft-java-fabric-claude-plugin/terrain-ecology"><img src="https://agentmods.dev/badge/skills/chapmanjw/minecraft-java-fabric-claude-plugin/terrain-ecology.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.00087 | $0.00653 |
| Opus 5 | $0.00044 | $0.00327 |
| Sonnet 5 | $0.00017 | $0.00131 |
| Haiku 4.5 | $0.00009 | $0.00065 |
Grade A, and why
terrain-ecology 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 8d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
terrain-ecology (Tier-3 leaf)
You own the ecological design decision over a finished heightfield + biome
assignment: which plant communities, species mixes, densities, and ecotone
transitions, emitted as a scatter recipe. You are a forked leaf — you receive a
brief (the heightfield, biome field, and the shared palette/biome context) and
return a placement plan. Read
${CLAUDE_PLUGIN_ROOT}/reference/terrain/ecology.md (your method) and
toolkit-api.md (the API).
Method
Drive ${CLAUDE_PLUGIN_ROOT}/tools/terrain (scatter.py, climate.py):
- Load the field + its
BiomeField(the orchestrator passes the recipe/biome plan). Do not re-decide the biomes — match them. scatter.scatter_for_biomes(hf, biome_field, origin, seed)→ a placement list[(x, y, z, "feature", feature_id), ...]. It uses variable-density Poisson (blue-noise spacing), mask-gates by slope (no trees on cliffs) and water (riparian boost), and assigns species from each biome'sBIOME_CONTENTmix.- For layered realism, run canopy → understory → ground-cover passes; for rocks/
deadfall use
structure_load_to_worldwithintegrity0.8–0.95. - Emit the placements into
plan.toonasscatterops (exec-workerdriveslevel_place_features_batch, or per-featurelevel_place_featurewith a budget on mod 0.3.0 — canopy first).
Non-negotiables
- Communities, not monoculture — a weighted species mix per stand.
- Grow, never place —
level_place_featureids so vanilla grows each tree. - Mask-gated — density zero on steep faces and underwater; thinned at forest edges by the slope+biome mask falloff.
- Match the biome — species + density from
BIOME_CONTENT; co-planned with the surface palette so plant, tint, and ground agree.
Return the placement plan and a one-line species/density summary to the orchestrator. Throughput note: a dense forest is hours of per-feature calls on mod 0.3.0 — prefer the batch tool; budget canopy-first otherwise.
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.
- 8d ago First seen · 54 lines · 87 tokens per session scan A e57a41c6475e
terrain-ecology is a skill published in the GitHub repository chapmanjw/minecraft-java-fabric-claude-plugin (6 stars, last pushed 11d ago), licensed MIT. It adds 87 tokens to every session and 653 once invoked, about $0.0004 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-dev
Use this skill whenever the user wants to look up Minecraft source, mod source, mod loader source, mappings, registries, versions, version differences, access transformers, mixin information, documentation, or code search results with minecraft-dev-cli. Also use it for Fabric, Forge, Quilt, and NeoForge source lookups.
ashfox
Create, edit, review, animate, and export game-ready low-poly assets in the ashfox web workbench through an AI agent. Use for low-poly modeling, deterministic textures and UVs, rigs, idle or motion animation, GLB, Bedrock, or GeckoLib exports, and Blockbench-free asset production.
1211-neoforge-modding
A development guide for creating Minecraft 1.21.1 mods with NeoForge, a Minecraft modding framework. It covers registering content, generating data, networking, capabilities, and crash diagnosis.
1201-forge-modding
A development guide for making Minecraft 1.20.1 mods with the Forge modding framework. It covers adding blocks, items, entities, recipes, network handling, and other standard mod features.
1201-mods-exsample
A reference for practical design patterns in Minecraft 1.20.1 Forge mod development. It draws examples from major mods and covers areas such as block entities, energy, interfaces, networking, recipes, rendering, spells, artificial intelligence, and scripting.
1211-mods-exsample
A reference for practical design patterns in Minecraft 1.21.1 NeoForge mod development. It also explains migration differences from Forge 1.20.1, including newer approaches to saved data, capabilities, and network messages.