hayba-pie-performance-capture

hayba-pie-performance-capture is a skill for Claude Code, Codex from zajalist/hayba. It costs 29 tokens per session (347 once invoked), scanned A, original, MIT.

A workflow for collecting repeatable performance samples from one Unreal route in PIE, or Play In Editor mode. It records world counts and bounded runtime samples so the same route can be compared before and after one change.

In plain words
What is it for?
Use it to capture a baseline, repeat the route after a controlled change, compare compatible snapshots, and inspect warnings, truncated samples, world changes, or aborted captures.
Why use it?
It prevents unlike test conditions from producing misleading performance comparisons. It also keeps editor statistics separate from runtime capture data and withholds a verdict when samples are incomplete or coverage differs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to capture a baseline, repeat the route after a controlled change, compare compatible snapshots, and inspect warnings, truncated samples, world changes, or aborted captures.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zajalist/hayba/hayba-pie-performance-capture
Install

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.

Any agent
npx skills add zajalist/hayba --skill hayba-pie-performance-capture
Clone the repo
git clone --depth 1 https://github.com/zajalist/hayba

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for hayba-pie-performance-capture

README.md
[![agentmods](https://agentmods.dev/badge/skills/zajalist/hayba/hayba-pie-performance-capture/github.svg)](https://agentmods.dev/skills/zajalist/hayba/hayba-pie-performance-capture)
Your own site
<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-pie-performance-capture"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-pie-performance-capture/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.

agentmods 80×15 button for hayba-pie-performance-capture

Your own site · 80×15
<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-pie-performance-capture"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-pie-performance-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 347 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00347
Opus 5.5 $0.00012 $0.00139
Sonnet 5.5 $0.00006 $0.00069
Haiku 4.5 $0.00003 $0.00035

Measured 13d ago against content hash f644de53d918, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hayba-pie-performance-capture 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.

mcp-tools/hayba-mcp/addons/workflows/hayba-pie-performance-capture/SKILL.md · 24 lines

What it actually says

Capture one repeatable PIE performance sample

When to use

Use when a change needs before/after evidence under the same map, route, viewport, quality settings, and machine load. Record target platform and actual frame or memory budget; if missing, report a baseline without a pass verdict.

Tool routing

  • Take world_budget_snapshot for loaded structural counts and record its coverage. Check editor_get_state, start editor_start_pie, settle the scene, then call editor_pie_capture_start for a bounded sample. Poll editor_pie_capture_get by its capture identifier until complete or aborted. Stop with editor_stop_pie after the capture.
  • Repeat the same route and sample count after one controlled change. Feed complete compatible snapshots and completed PIE captures to world_compare_snapshots. If scan coverage or captures differ, keep the observed values but withhold the delta verdict. Use editor_get_performance_stats as a separate editor metric, not as interchangeable frame time.
  • Inspect warnings, truncated samples, world changes, and aborted captures before concluding anything. A safety refusal while the editor is unsafe is a stop signal, not permission to retry in a loop.

Evidence

Report protocol, capture identifiers and status, sample counts, timing and physical-memory proxies, structural coverage, comparison result, and unknowns. These are whole-editor measurements: GPU time, real World Partition cells, NPC AI cost, packaged-build memory, and a production-performance verdict remain unmeasured.

Changes

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.

  1. 13d ago First seen · 24 lines · 29 tokens per session scan A f644de53d918

Subscribe to this mod's changes

hayba-pie-performance-capture is a skill published in the GitHub repository zajalist/hayba (13 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 347 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.

Related

Other skills, from other repositories

unreal-mcp

Automate Unreal Engine editor scenes, actors, and renders.

NousResearch/hermes-agent · 17 tokens

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.…

kevinpbuckley/VibeUE · 130 tokens

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.

kevinpbuckley/VibeUE · 64 tokens

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…

kevinpbuckley/VibeUE · 95 tokens

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…

kevinpbuckley/VibeUE · 82 tokens

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…

kevinpbuckley/VibeUE · 61 tokens