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-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/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-debug-level"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-debug-level.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.00029 | $0.00361 |
| Opus 5.5 | $0.00012 | $0.00144 |
| Sonnet 5.5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
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 22d 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
Diagnose a level symptom
When to use
Use for a concrete symptom such as floating objects, overlaps, missing generated content, low frame rate, or a streaming gap. Record the camera, active map, and reproduction steps so a later readback is comparable.
Tool routing
- Start with
hayba_check_ue_status. Gather a baseline througheditor_get_performance_stats,editor_stream_log, andscene_exportin hierarchical mode. Usewp_get_cellswhen World Partition is relevant. - For placement symptoms, run
scene_validate_physics; inspect affected actors withactor_listandplacement_validatebefore consideringactor_transformoractor_set_visibility. A position that looks unusual may be an intentional user adjustment. - For generated content, use the hayba-pcg-build skill and a fresh cook readback. For performance, change one suspected cause at a time, then repeat the same measurement conditions.
- For an accepted map repair, read back the changed actor or generated output, call
level_savefor the exact active map, and inspect saved, dirty, and verified status. If persistence cannot be checked safely, report the repair as unsaved and route it to hayba-world-save-integrity.
Evidence
Give the original symptom, baseline values or findings, the smallest confirmed cause, the edit made, and the after measurement. Run validator_run after scene edits. If measurements are unavailable, leave the diagnosis as a hypothesis rather than calling the level fixed.
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.
- 22d ago Changed · +8 lines · -8 tokens per session 6d49a1c1b8d6
- 1mo 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 (13 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 361 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-08-30.
Other skills, from other repositories
blueprint-reader
Read, explain, trace, debug, and plan edits to Unreal Engine Blueprint graphs from blueprintue.com links or raw Begin Object / End Object clipboard text, including attached text documents and macro bodies. Generate a compact AI brief, plain-language overview, evidence-based improvement tips, or a local paste/link…
debug-unreal-pie-with-python
Control and debug one in-process Unreal Engine Play In Editor or Simulate session through Loomle Python after applying the use-unreal-python safety workflow. Use when reproducing gameplay, querying runtime Actors or components, invoking gameplay APIs, checking state across frames, or managing PIE start and stop.
mc-modpack-helper
A diagnostic workflow for Minecraft Fabric and Forge modpacks, which are collections of Minecraft modifications. It checks Java versions, conflicting or missing mods, outdated files, launch settings, and crash logs.
debug-issue
Systematic Godot debugging decision trees for physics, signals, rendering, navigation, and input issues.
unreal-performance-profiling
Use when an Unreal Engine project has low frame rate, hitches, stalls, memory growth, long loads, excessive draw calls, shader or overdraw cost, expensive AI or Blueprint work, or needs an evidence-based performance budget.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.