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 amenti-labs/vibecraft --skill building-structuresgit clone --depth 1 https://github.com/amenti-labs/vibecraftWrote 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/amenti-labs/vibecraft/building-structures)<a href="https://agentmods.dev/skills/amenti-labs/vibecraft/building-structures"><img src="https://agentmods.dev/badge/skills/amenti-labs/vibecraft/building-structures.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.01774 |
| Opus 5 | $0.00030 | $0.00887 |
| Sonnet 5 | $0.00012 | $0.00355 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
building-structures 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Structures
Primary Method: Schematics
Use build_schematic() for all structures. See building-with-schematics skill for schema details.
Critical: Floor Y = Ground Y
Floor REPLACES ground, NOT sits on top!
WRONG: Y=65 floor, Y=64 foundation, Y=63 grass (elevated!)
RIGHT: Y=65 walls, Y=64 floor REPLACES grass, Y=63 dirt
Workflow: get_surface_level(x,z) → anchor at that Y
Pre-Build Checklist
-
get_surface_level()called - anchor_y = ground_y (NOT +1)
- All blocks have orientations
- Doors have lower + upper
- Preview first (
preview_only=true)
Building Workflow
# 1. Get ground level
y = get_surface_level(x=100, z=200)
# 2. Design schematic
schematic = {
"anchor": [100, y, 200],
"palette": {
"S": "stone_bricks",
"P": "oak_planks",
"W": "oak_planks",
"G": "glass_pane",
"Dl": "oak_door[facing=south,half=lower]",
"Du": "oak_door[facing=south,half=upper]",
"Sn": "oak_stairs[facing=north,half=bottom]",
"Ss": "oak_stairs[facing=south,half=bottom]",
".": "air"
},
"layers": [
# y=0: Foundation/Floor
{"y": 0, "grid": [
["S", "S", "S", "S", "S"],
["S", "P", "P", "P", "S"],
["S", "P", "P", "P", "S"],
["S", "S", "S", "S", "S"]
]},
# y=1-3: Walls
{"y": 1, "grid": [
["W", "W", "W", "W", "W"],
["W", ".", ".", ".", "W"],
["G", ".", ".", ".", "G"],
["W", "W", "Dl", "W", "W"]
]},
# ... more layers
]
}
# 3. Preview
build_schematic(schematic=schematic, preview_only=true, description="Cottage")
# 4. Execute
build_schematic(schematic=schematic, description="Cottage")
Dimensions Reference
| Room Type | Minimum | Comfortable |
|---|---|---|
| Bedroom | 5×6 | 6×7 |
| Kitchen | 5×7 | 6×8 |
| Living Room | 7×9 | 8×10 |
| Dining | 7×9 | 8×10 |
| Great Hall | 15×20 | 20×25 |
| Ceiling Height | Feel |
|---|---|
| 3 blocks | Minimum |
| 4 blocks | Comfortable |
| 5-6 blocks | Grand |
| 8+ blocks | Cathedral |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 257 lines · 59 tokens per session scan A 0bf06953604c
building-structures is a skill published in the GitHub repository amenti-labs/vibecraft (98 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 1,774 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-30.
Other skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.