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-foliage-layoutgit 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-foliage-layout)<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-foliage-layout"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-foliage-layout/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-foliage-layout"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-foliage-layout.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.00030 | $0.00369 |
| Opus 5.5 | $0.00012 | $0.00148 |
| Sonnet 5.5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
hayba-foliage-layout 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
Lay out foliage
When to use
Use for a bounded region with known ground and a visual goal. Identify traversable space, sightlines, and no-scatter zones first. Ask for a density or performance target if one matters; otherwise treat density as a trial parameter.
Tool routing
- Inspect the region with
scene_export,foliage_list_types, andeditor_capture_viewport. Select only available foliage assets or request a suitable asset choice. - Use
foliage_paint_atfor a controlled patch. A PCG graph is a better choice when the area must regenerate by seed, cover many cells, or express repeated spatial rules. - Read back the scene and capture the same camera. Run
scene_validate_physicsandvalidator_runfor scene effects, then compareeditor_get_performance_statsunder the same editor conditions if a performance budget was supplied. - After accepting the patch, save the exact active map through
level_save, inspect saved, dirty, and verified status, then re-read the foliage type/count and scene withfoliage_list_typesandscene_export. If the save or external actor coverage is uncertain, mark the patch unsaved and route it to hayba-world-save-integrity.
Evidence
Record the region, asset types, intended and observed density, visible route clearance, and measured frame/draw-call change if available. A successful paint response does not prove the intended coverage; inspect the result. Stop after one pilot patch before expanding across the level.
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 · 30 tokens per session scan A 112485ee0660
hayba-foliage-layout is a skill published in the GitHub repository zajalist/hayba (13 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 369 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
unreal-mcp
Automate Unreal Engine editor scenes, actors, and renders.
asset-management
Import files from disk (images, meshes, any format the editor imports), export textures, query the Content Browser selection, and check if an asset is open (AssetDiscoveryService). Search, load, save, move, rename, duplicate, and delete assets are handled by Unreal's native AssetTools toolset or EditorAssetLibrary.…
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…
vibeue
Unreal Engine 5 development using the VibeUE Python API. Use when working in Unreal Engine — blueprints, state trees, materials, actors, landscapes, animation, niagara, widgets, sound, foliage, gameplay tags, enhanced input, skeletons, PCG (procedural content generation), and more. VibeUE is an extension of Unreal's…
project-settings
Configure Unreal Engine project settings and editor preferences — UI appearance, toolbar icons, scale, colors, and any UDeveloperSettings subclass (ProjectSettingsService). Use when the user asks to change a project setting or editor preference, configure a UDeveloperSettings category, or read/write project config…