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-project-cook-readinessgit 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-project-cook-readiness)<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-project-cook-readiness"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-project-cook-readiness/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-project-cook-readiness"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-project-cook-readiness.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.00032 | $0.00332 |
| Opus 5.5 | $0.00013 | $0.00133 |
| Sonnet 5.5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
hayba-project-cook-readiness 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.
What it actually says
Check cook readiness
When to use
Use before a milestone build for a named platform and configuration. Record the exact target, expected maps and content, known baseline, and pass criteria. A successful cook is only one gate toward a shippable build.
Tool routing
- Read project_get_info and project_get_settings for the target context. Run content_validate and validator_run on the relevant content, then inspect asset_get_dependencies for assets named in any warning or error. Fix the specific fault with focused tools and re-run that check.
- Read get_tool_signature for the platform and cook scope, then start build_cook only after the target is settled. It returns a background job identifier; poll build_status until it reaches a terminal result. Inspect exit code and diagnostic output, not just job creation. If the call's outcome is uncertain, query build_status for the same job before starting another cook.
- Where a code build is required, run build_project separately and poll its job through build_status. Preserve warnings and skipped validations in the report. This workflow does not package, sign, deploy, or certify a release.
Evidence
Report platform/configuration, validation results, job identifier, terminal exit code, relevant errors and warnings, and unresolved assets. A zero-exit cook does not prove gameplay, frame rate, memory, console certification, or distributable packaging.
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.
- 13d ago First seen · 24 lines · 32 tokens per session scan A ddbedf93ce38
hayba-project-cook-readiness is a skill published in the GitHub repository zajalist/hayba (13 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 332 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.
Other skills, from other repositories
unreal-mcp
Automate Unreal Engine editor scenes, actors, and renders.
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.…
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…
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…