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 SummerEngine/summer-engine-agent --skill prop-modelgit clone --depth 1 https://github.com/SummerEngine/summer-engine-agentWrote 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/summerengine/summer-engine-agent/prop-model)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/prop-model"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/prop-model.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.00089 | $0.02172 |
| Opus 5 | $0.00044 | $0.01086 |
| Sonnet 5 | $0.00018 | $0.00434 |
| Haiku 4.5 | $0.00009 | $0.00217 |
Grade A, and why
prop-model 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prop Model — Generate One Static 3D Prop and Wire It
One prop, one mesh, one MeshInstance3D. This is the bread-and-butter call of the 3D-asset family — most game-world objects are static props. The skill exists to keep two things tight: the prompt shape that produces a clean isolated mesh on the first try, and the wire-in pattern that gets the asset into the scene without leaving orphans in res://assets/models/.
The backing tool is summer_generate_3d. Default model is hunyuan (Hunyuan 3D v3.1 Pro — best quality). Use trellis when speed matters (Trellis 2 is ~2× faster, slightly lower fidelity). meshy is the legacy fallback — only pick it if the user asks by name.
When to use
- "Make me a treasure chest."
- "Generate a viking axe."
- "I need a wooden barrel for the cellar."
- "Create a sci-fi crate."
- Any single, static, non-character, non-modular object the player will see in 3D space.
When NOT to use
- Character / humanoid →
summer:3d-assets/character-model(needs T-pose + rig pass). - A set of matching pieces (walls, floors, doors, pillars) →
summer:3d-assets/environment-kit(style-locked family). - Trees, rocks, foliage →
summer:3d-assets/organic-model(organic forgives AI artifacts; cheaper recipe). - Cars, ships, mechs →
summer:3d-assets/vehicle-model(hard-surface specifics). - Walls / floors / repeating geometry →
summer:asset-pipeline/asset-strategyPipeline 2 (textures + CSG). - "I just need a placeholder" → propose a primitive (
BoxMesh/CylinderMesh) instead. Generation is metered.
Steps
1. Search before generating
summer_search_assets(query="<prop name>", assetType="3d_model", source="all")
If a fitting model exists, propose reuse:
Found
assets/models/treasure_chest_01.glb. Reuse this, or generate fresh?
2. Pick a polycount target
| Use case | Tris | Pass via |
|---|---|---|
| Hero prop (sword on hip, key item) | 3k–8k | options: { target_polycount: 5000 } |
| Background prop (crate, barrel, sack) | 200–800 | options: { target_polycount: 600 } |
| Mid-range interactive (chest, lantern) | 1k–3k | options: { target_polycount: 2000 } |
| Cinematic showcase (throne, statue) | 10k–30k | options: { target_polycount: 20000 } |
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 · 148 lines · 89 tokens per session scan A dc97d87cce31
prop-model is a skill published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 2,172 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-30.
Other skills, from other repositories
self-evolve
Capture reusable patterns from a finished project and lift them into framework-level priors (contracts, modules, skeletons) that future projects inherit. Run only when the user explicitly requests self-evolution; the orchestrator executes the workflow.
artist-self-evolve
Distill stable art-generation patterns from a completed project, so future projects produce comparable assets without re-discovering the prompts. Lead-dispatched only — orchestrator invokes this skill from its self-evolve flow with a game-slug message; do not self-trigger.
vibegame-build
Run VibeGame's standard end-to-end game development workflow with reviewer gates. Use when the user wants to create a game from zero or evolve an existing game across multiple stages.
vibegame-start
Resume a VibeGame orchestrator session after vibegame start. Use at the beginning of a Claude or Codex session to inspect team runtime state, repair missing persistent members, load goal and GDD context, inspect tasks, and ask the user what to do next.
vibegame-edit
Iterate broadly on an existing game, on top of vibegame-build. Use when the user asks to change an existing game's art style, genre, or core rules. Not for local tuning such as numbers or game feel. Orchestrator only.
hearth-art
Give a Hearth game real art and sound — importing and slicing spritesheets, animations, procedural sprites and sounds, autonomous CC0 asset sourcing (Kenney, itch.io, OpenGameArt, Freesound, Google Fonts) with licensing rules, and pixel-art discipline (never stretch; read the art before using it). Use when the game…