Borrowing it
Nothing to install: this file belongs to ukanwat/aaabench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ukanwat/aaabench/main/.claude/skills/unreal-niagara/SKILL.mdgit clone --depth 1 https://github.com/ukanwat/aaabenchWrote 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/ukanwat/aaabench/unreal-niagara)<a href="https://agentmods.dev/skills/ukanwat/aaabench/unreal-niagara"><img src="https://agentmods.dev/badge/skills/ukanwat/aaabench/unreal-niagara/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/ukanwat/aaabench/unreal-niagara"><img src="https://agentmods.dev/badge/skills/ukanwat/aaabench/unreal-niagara.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.00085 | $0.01458 |
| Opus 5.5 | $0.00034 | $0.00583 |
| Sonnet 5.5 | $0.00017 | $0.00292 |
| Haiku 4.5 | $0.00009 | $0.00146 |
Grade A, and why
unreal-niagara 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 1mo 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.
This is a copy
92% identical to unreal-niagara — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unreal Niagara VFX
Build and control real-time visual effects in UE5 with Niagara: understand the System/Emitter/Module hierarchy, expose parameters you can drive from gameplay, and spawn effects at runtime. Targets UE 5.4+. (Niagara replaces the legacy Cascade system.)
When to use
- Use when creating a Niagara System (
NS_) and Emitters (NE_), wiring modules in the spawn/update stages, exposing User parameters to gameplay, or spawning/driving an effect (impact, muzzle flash, fire, magic) from Blueprint or C++. - Use when the project has Niagara
NS_/NE_assets or referencesUNiagaraComponent.
When not to use: material/shader authoring (the look of a surface, not particles) is a
separate topic; shader-programming covers cross-engine shader concepts. Audio for the effect
→ audio-design.
Core workflow
- Understand the hierarchy. A Niagara System (
NS_) is the effect you place/spawn; it contains one or more Emitters (NE_, often emitter templates). Each emitter runs in stages: Emitter Spawn/Update, Particle Spawn/Update, optional Event Handler, and Render. - Build behaviour from Modules, which execute top-to-bottom in each stage (Spawn Rate, Add Velocity, Gravity Force, Color over Life, etc.). Order matters — a later module reads the values earlier ones wrote.
- Know the parameter namespaces:
System,Emitter,Particle, andUser. Only User-namespace parameters are exposed to and settable from Blueprint/C++; the others are internal to the simulation. - Spawn at runtime with
UNiagaraFunctionLibrary::SpawnSystemAtLocation(world position) orSpawnSystemAttached(follows a component/socket), which return aUNiagaraComponent. - Drive the effect by setting its User parameters on the returned component (color, spawn
rate, a target position) and
Activate/Deactivateit. - Verify in the Niagara editor preview and in-level; check bounds (especially GPU emitters), and confirm the effect culls/destroys correctly.
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.
- 1mo ago First seen · 130 lines · 85 tokens per session scan A 39a0c0e390d7
unreal-niagara is a skill published in the GitHub repository ukanwat/aaabench (385 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 1,458 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to unreal-niagara, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
unreal-engineer
!cat skills/shared/protocols/3d-spatial-foundations.md 2>/dev/null || echo "=== 3D Foundations not loaded ===".
unreal-playtest-agent
Domain skill - run screenshot-light PIE playtest episodes with structured entity observations, bounded semantic actions, transition polling, and in-memory traces for QA and external policy or RL runners.
unreal-level
Domain skill - Unreal Engine level and world management: inspect level state, load and save maps, read or edit world settings, and measure native collision distances in Editor or PIE worlds. Not for individual actor transform edits - use unreal-actors for that.
unreal-pie
Domain skill - Unreal Engine Play-In-Editor (PIE) closed-loop verification. Provides PIE lifecycle control (enter/pause/resume/exit), controlled input injection (no OS dependency), viewport screenshot capture, output log snapshot, performance sampling, and Automation Test execution with async job polling. Use for…
unreal-actors
Domain skill - Unreal Engine actor management: list, spawn, transform, and delete level actors. Use when inspecting or editing actors in the current Unreal Editor level. Not for Content Browser asset import/export - use unreal-assets for that.
unreal-assets
Domain skill - Unreal Engine Content Browser asset management: list, import, export, inspect, and delete assets. Use for package and asset operations in the Unreal Editor. Not for actor placement or transforms - use unreal-actors for that.