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 teixasalone/UnrealEngine5-Skills --skill ue5-blueprint-workflowgit clone --depth 1 https://github.com/teixasalone/UnrealEngine5-SkillsWrote 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/teixasalone/unrealengine5-skills/ue5-blueprint-workflow)<a href="https://agentmods.dev/skills/teixasalone/unrealengine5-skills/ue5-blueprint-workflow"><img src="https://agentmods.dev/badge/skills/teixasalone/unrealengine5-skills/ue5-blueprint-workflow/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/teixasalone/unrealengine5-skills/ue5-blueprint-workflow"><img src="https://agentmods.dev/badge/skills/teixasalone/unrealengine5-skills/ue5-blueprint-workflow.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.00058 | $0.01087 |
| Opus 5.5 | $0.00023 | $0.00435 |
| Sonnet 5.5 | $0.00012 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
ue5-blueprint-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Start
- Identify target Blueprint asset and graph (
EventGraphor function graph). - Confirm requested behavior as event -> logic -> output chain.
- Decide input route first: legacy key event or Enhanced Input action event.
- Produce graph-level steps first, then exact node/pin wiring details.
UE5.7 API Anchors
- Keyboard and event node anchors:
UK2Node_InputKey,UK2Node_InputAction,UK2Node_InputActionEventUK2Node_CallFunction,UK2Node_CustomEvent
- Enhanced Input anchors:
UInputAction,UInputMappingContextUEnhancedInputLocalPlayerSubsystem::AddMappingContext(...)UEnhancedInputLocalPlayerSubsystem::RemoveMappingContext(...)UEnhancedInputComponent::BindAction(...)
- Tool fast-path anchors (preferred for Blueprint editing automation):
blueprint_modifywithoperation=add_input_key_eventblueprint_modifywithoperation=connect_pinsblueprint_queryfor pin inspection and compile checks
Graph Stage Contract
- Every requested Blueprint feature must specify:
- Entry event source (key/input action/custom event)
- Core logic nodes (minimum two meaningful nodes)
- Required pin-level connections (exec and data pins)
- Output/side effects (state change, call, spawn, UI)
- Validation method (compile status, node/pin inspection, expected execution order)
- If any item is missing, the graph implementation is incomplete.
Workflow
1) Entry Event
- Keyboard requests: use
add_input_key_eventfirst withreuse_existing=true. - Enhanced Input requests: add/reuse Input Action event nodes (
UK2Node_InputActionEventpath). - Do not perform generic event-node guessing before trying dedicated input operations.
2) Core Logic Chain
- Build minimal deterministic logic with explicit control flow (
Branch,Sequence, function calls). - Prefer existing graph variables/functions over creating redundant nodes.
- Keep one clear execution path per behavior branch.
3) Pin Wiring
- Connect exec pins before data pins to lock execution order.
- Inspect exact pin names via
blueprint_querybeforeconnect_pins. - Avoid ambiguous autowiring when multiple overload pins exist.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 96 lines · 58 tokens per session scan A cccaf6a621b6
ue5-blueprint-workflow is a skill published in the GitHub repository teixasalone/UnrealEngine5-Skills (20 stars, last pushed 16d ago), licensed MIT. It adds 58 tokens to every session and 1,087 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
scenario-blender-retopology
Use when turning a dense sculpt, scan or AI-generated mesh into clean topology in Blender, for animation, subdivision or a game low poly with a triangle budget. Also when choosing between QuadriFlow or voxel remesh and manual retopo, placing loops around eyes, mouth and joints, deciding pole placement, setting up a…
scenario-maya-retopology-uv
Use when turning a dense sculpt, scan, ZBrush export or AI-generated mesh into animation-ready or game-ready topology in Maya without a mouse ("clean up this AI mesh", "retopo this character", Quad Draw, Retopologize), testing it deforms before rigging (bad elbow or wrist bend, lids popping through the eyes), or…
scenario-zbrush-expert
Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…
scenario-godot-expert
Use when an agent drives Godot 4.7 on macOS or Windows for any task: headless --script jobs, --import, --check-only, command-line exports, GUT tests, windowed screenshots, the headless editor (-e) or an MCP server into a running editor; when a run hangs or fails silently, a capture is black, Godot 3 code breaks in…
scenario-roblox-tooling
Use when setting up or repairing a Roblox team project outside Studio: Rojo or Script Sync, Wally packages, Rokit pins, luau-lsp type checking, Selene, StyLua, unit tests in Lune or the engine, GitHub Actions CI on pull requests, Open Cloud place publishing, Luau Execution or API key scopes, merging builders' Team…
scenario-blender-hair
Use when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games. Also covers the Essentials hair node assets (Interpolate, Clump, Curl, Frizz, Noise, Trim), density masks, bald spots, parting lines, strand…