Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/asteroid-belt/skultonpx agentmods add skills/asteroid-belt/skulto/autobuildWrote 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/asteroid-belt/skulto/autobuild)<a href="https://agentmods.dev/skills/asteroid-belt/skulto/autobuild"><img src="https://agentmods.dev/badge/skills/asteroid-belt/skulto/autobuild/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/asteroid-belt/skulto/autobuild"><img src="https://agentmods.dev/badge/skills/asteroid-belt/skulto/autobuild.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00064 | $0.04430 |
| Opus 5 | $0.00032 | $0.02215 |
| Sonnet 5 | $0.00013 | $0.00886 |
| Haiku 4.5 | $0.00006 | $0.00443 |
Grade A, and why
autobuild 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- autobuild — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 662 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autobuild: Autonomous Plan Execution Engine
Execute entire implementation plans in a single pass with zero user intervention. Each phase runs in its own sub-agent, writing state to the filesystem. Context never exhausts because sub-agents are isolated.
Overview
Autobuild is an autonomous execution engine for superplan implementation plans. Unlike superbuild which stops after each phase for user confirmation, autobuild runs everything to completion.
Key Differences from superbuild:
| Aspect | superbuild | autobuild |
|---|---|---|
| Execution | Phase-by-phase with stops | Continuous until complete |
| User intervention | Required after each phase | None (fully autonomous) |
| Context management | Manual compaction | Sub-agents isolate context |
| State persistence | In conversation | Filesystem (.autobuild/) |
| Resume capability | Manual | Automatic from state files |
Reference Index - MUST READ When Needed
References contain detailed templates and patterns. Read BEFORE you need them.
| When | Reference | What You Get |
|---|---|---|
| Step 1: Initialize | STATE-FILES.md | State file format, directory structure |
| Step 3: Execute phases | PHASE-EXECUTION.md | Phase ordering, parallel detection, retry logic |
| Step 3: Launch sub-agents | SUBAGENT-PROMPTS.md | Exact prompts for phase sub-agents |
| Step 4: Verify and commit | VERIFICATION.md | Fresh verification, commit handling |
| Step 5: Handle failures | FAILURE-HANDLING.md | Retry logic, error recovery |
| Overall flow | ORCHESTRATION.md | Main orchestration loop, completion handling |
Also reference superplan documents:
superplan/references/TASK-MICROSTRUCTURE.md- TDD 5-step format per tasksuperplan/references/TDD-DISCIPLINE.md- TDD enforcement rulessuperbuild/references/ENFORCEMENT-GUIDE.md- Quality gate commands by stack
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 662 lines · 64 tokens per session scan A 11be6afe4d26
autobuild is a skill published in the GitHub repository asteroid-belt/skulto (50 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 4,430 once invoked, about $0.0003 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
test-skill
A test skill for validation.
different-name
This has a mismatched name.
run-skill-script
Execute a skill's script file with arguments. When you need to run skill functionality, execute specific operations, or process data with skill.
install-skill
Install skill from URL or Git repository to local skills/ directory. When you need to add new skill from GitHub or install SKILL.md from URL. Supports Git repos and single SKILL.md files.
get-skill-info
Get skill detailed instructions and usage guide (Level 2 disclosure). When you need to understand how to use a skill, check skill capabilities, or learn skill parameters.
load-skill
Load a newly created skill from skills/ directory to make it immediately available.