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 valkor-ai/loom --skill headless-buildgit clone --depth 1 https://github.com/valkor-ai/loomWrote 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/valkor-ai/loom/headless-build)<a href="https://agentmods.dev/skills/valkor-ai/loom/headless-build"><img src="https://agentmods.dev/badge/skills/valkor-ai/loom/headless-build.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.00085 | $0.00466 |
| Opus 5 | $0.00043 | $0.00233 |
| Sonnet 5 | $0.00017 | $0.00093 |
| Haiku 4.5 | $0.00009 | $0.00047 |
Grade A, and why
headless-build 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 7d 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
Headless Build
Compile-check a Godot project. Fastest feedback loop: "did my code parse?"
Run
Use GODOT_PATH when Godot is not on PATH:
GODOT_BIN="${GODOT_PATH:-godot}"
"$GODOT_BIN" --headless --path . --editor --quit 2>&1
Run from the project root (where project.godot lives). Should exit within 30 seconds.
If it hangs, an autoload may block in _ready() — kill and report.
Filter output
Godot's output mixes script errors with engine noise. Only script errors matter.
Ignore these (engine internals, always present in headless mode):
Condition "..." is truewith.cppsource location — engine C++ assertionObjectDB instances leaked at exit— no cleanup in headlessN resources still in use at exit— same causeScreen index N is invalid— no display in headless
Rule: if the at: line references a .cpp file, skip it.
These ARE script errors (report them):
SCRIPT ERROR:withres://path — GDScript parse/load failureFailed to load script "res://..."— missing or broken scripterror CS— C# build error (from dotnet build)Failed to load resource "res://..."— missing dependency
Report
- No script errors → PASS
- Script errors found → FAIL, list each with file, line, message
- Don't auto-fix. Report only.
- Ignore
WARNING:lines and application log output.
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.
- 7d ago First seen · 53 lines · 85 tokens per session scan A 5964c2ff21c9
headless-build is a skill published in the GitHub repository valkor-ai/loom (968 stars, last pushed 21d ago), licensed Apache-2.0. It adds 85 tokens to every session and 466 once invoked, about $0.0004 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
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.