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 agentmods add skills/zajalist/hayba/hayba-debug-levelnpx skills add zajalist/hayba --skill hayba-debug-levelgit 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-debug-level)<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-debug-level"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-debug-level.svg" alt="Measured on agentmods" 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.00037 | $0.00196 |
| Opus 5 | $0.00018 | $0.00098 |
| Sonnet 5 | $0.00007 | $0.00039 |
| Haiku 4.5 | $0.00004 | $0.00020 |
Grade A, and why
hayba-debug-level 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 5d 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
hayba-debug-level
Workflow
editor_get_performance_stats— baseline FPS / draw calls / memory.editor_stream_logfiltered byLogStreaming|LogPhysics|LogPCG— start tail.scene_validate_physics(no deep check first).scene_exportmode "hierarchical" — look for over-dense cells.- For floating actors:
actor_transformto snap to ground (useplacement_validatefirst). - For interpenetration:
actor_transformoractor_set_visibilitybased on context. - For perf hotspots: check
wp_get_cellsfor heavy cells; consider ISM consolidation opportunities (ism_*).
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.
- 5d ago First seen · 17 lines · 37 tokens per session scan A cd7c00161cca
hayba-debug-level is a skill published in the GitHub repository zajalist/hayba (12 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 196 once invoked, about $0.0002 per session on Opus 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
unreal-mcp
Automate Unreal Engine editor scenes, actors, and renders.
asset-management
Import/export textures crash-safely, 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. Use when the user asks to import an image from disk…
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…
gameplay-tags
Create, list, remove, and rename Gameplay Tags with runtime registration (GameplayTagService). Use when the user asks to add or register gameplay tags, list/query existing tags, or rename/remove tags (e.g. Ability.Attack.Melee, State.Stunned).