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-asset-import-vettinggit 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-asset-import-vetting)<a href="https://agentmods.dev/skills/zajalist/hayba/hayba-asset-import-vetting"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-asset-import-vetting/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-asset-import-vetting"><img src="https://agentmods.dev/badge/skills/zajalist/hayba/hayba-asset-import-vetting.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.00033 | $0.00391 |
| Opus 5.5 | $0.00013 | $0.00156 |
| Sonnet 5.5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
hayba-asset-import-vetting 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
Vet one imported asset
When to use
Use for a specific mesh, texture, or audio source that the project is allowed to use. Record source provenance and license outside the editor, intended package path, asset type, target platform, and an agreed triangle, texture, or audio budget. Do not infer usage rights from a successful download or import.
Tool routing
- Check asset_search and asset_get_info for a collision at the destination. Inspect the source with asset_get_source_path where an asset already exists. Use get_tool_signature before asset_import: that importer accepts one supported file from its connector cache under a bounded policy and refuses overwrite; it is not a general arbitrary-file sanitizer.
- Import once with asset_import. Inspect the returned exact asset path, class, save state, and warnings before any retry. A dirty in-memory result needs asset_save. Re-query that exact path with asset_get_info and use asset_validate plus asset_get_dependencies to find missing references.
- For a mesh, run mesh_audit and inspect LOD/UV/material facts. For a texture, run texture_audit and texture_get_info. Compare the result with the stated platform budget; route further tuning to the matching focused skill. Use asset_get_referencers before replacing or moving an existing asset.
Evidence
Return source and license evidence, exact package path and class, import warnings, validation findings, dependencies, saved status, and relevant quality measurements. An importer success does not prove a remote file is safe to parse, that the asset is visually suitable, or that it fits runtime memory. If source trust or rights are unresolved, stop before importing it into the editor.
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 · 33 tokens per session scan A 03575542cd4e
hayba-asset-import-vetting is a skill published in the GitHub repository zajalist/hayba (13 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 391 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…