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-niagara-vfx-passgit 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-niagara-vfx-pass)<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-niagara-vfx-pass"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-niagara-vfx-pass/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-niagara-vfx-pass"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-niagara-vfx-pass.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.00407 |
| Opus 5.5 | $0.00012 | $0.00163 |
| Sonnet 5.5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
hayba-niagara-vfx-pass 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
Place one Niagara effect
When to use
Use for a specific gameplay signal or environmental effect with a target position, duration, scale, and readability requirement. Record the target platform, maximum simultaneous instances, and visual or frame budget if supplied.
Tool routing
- Start with niagara_capability_probe and niagara_systems, then inspect the chosen asset through niagara_system_inspect and niagara_validate. Treat missing emitter or exposed-parameter reflection as an information gap, not a clean validation pass. Prefer an existing system over creating a new template asset for a placement task.
- Place a persistent level effect with niagara_place_actor; use niagara_spawn_transient only for a throwaway preview. Check asset-assigned and warning fields after placement. Use niagara_param_list before niagara_param_set on a live component, and require its applied flag before accepting the change.
- Re-inspect the component with niagara_component_inspect, capture the same view with editor_capture_viewport, and measure editor_get_performance_stats in the target scene. Use an actual PIE trigger for a gameplay effect whose timing matters; a still image cannot establish spawn or fade behavior.
- For an accepted persistent actor or component change, save the exact active map through level_save, inspect saved, dirty, and verified status, and re-inspect the component. A transient preview needs no map save. If persistence is uncertain, mark the placement unsaved and route it to hayba-world-save-integrity.
Evidence
Report system and actor paths, validation violations, applied parameters, visible result, instance assumptions, and measured cost. If fixed bounds, effect type, or emitter reflection remains uncertain, carry that warning forward rather than calling the VFX production ready.
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 4d90b53910e5
hayba-niagara-vfx-pass 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 407 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…