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 zajalist/hayba --skill hayba-hero-set-dressinggit clone --depth 1 https://github.com/zajalist/haybaWrote 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/zajalist/hayba/hayba-hero-set-dressing)<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-hero-set-dressing"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-hero-set-dressing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-hero-set-dressing"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-hero-set-dressing.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00366 |
| Opus 5.5 | $0.00012 | $0.00146 |
| Sonnet 5.5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
hayba-hero-set-dressing 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 13d 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.
What it actually says
Dress a focal area
When to use
Use for a plaza, room, vista, encounter anchor, or other authored focal space. Determine the view and the playable clearance before adding pieces. Preserve the ownership boundary if nearby content is generated by PCG.
Tool routing
- Read
scene_exportand capture the current camera witheditor_capture_viewport. Search project assets throughhayba_asset_search; verify class, scale, and path before selection. - Place a content asset with
actor_spawn_from_asset, then useplacement_validateandscene_validate_physicsto check grounding and intersections.actor_transformis appropriate for a small correction after the exact actor is identified. Prefer fewer purposeful pieces when repeated detail weakens the focal point. - If the area needs a broad repeated field, hand that portion to hayba-foliage-layout or hayba-pcg-build. Keep individually authored hero actors outside regenerated ownership.
- Once placements are accepted, save the exact active map with
level_save, inspect saved, dirty, and verified status, and re-read the placed actors withactor_listoractor_inspect. If persistence remains uncertain, mark the layout unsaved and route it to hayba-world-save-integrity.
Evidence
Report chosen asset paths, placement counts, before/after captures from the same viewpoint, and any collisions or clearance concerns. Run validator_run after placement. Stop after one coherent focal pass and one correction pass unless the user asks for further exploration.
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.
- 13d ago First seen · 25 lines · 31 tokens per session scan A 76a4d046ad0e
hayba-hero-set-dressing is a skill published in the GitHub repository zajalist/hayba (13 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 366 once invoked, about $0.0001 per session on Opus 5.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-10-04.
Other skills, from other repositories
controller-ui
Use when building or reviewing Air Jam controller surfaces so touch controls stay simple, readable, and game-appropriate instead of drifting into dense web-app UI patterns.
host-surface
Use when building or reviewing the Air Jam host shell so the active game surface stays full-frame, overlays stay modular, and host UI does not interfere with gameplay layout.
pn-spatial-ux-patterns
Spatial interaction design, AR/VR/XR UX patterns. Depth, scale, ergonomics, interaction zones, text legibility. Use for immersive interface design.
ux-design
Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.
level-actors
List, find, place, move, rotate, and modify actors in the current level (ActorService + editor subsystems). Use when the user asks to find/list actors in the level, move or rotate an actor, set an actor's properties/folder/transform, or spawn/delete level actors.
materials
Create and edit materials and material instances — graph nodes, parameters, functions, custom HLSL, and instance overrides (MaterialService + MaterialNodeService). Use when the user asks to create or edit a material/material instance, wire material nodes, add material parameters, set blend/shading modes, or recreate a…