skills.sh
AvailableUniversal skill installation, including Claude Code and Codex.
npx skills add https://github.com/ulpi-io/skills-autonomous-engineering --skill budget-guardbudget-guard
Declares and enforces the five stop conditions that keep unattended work from becoming runaway work.
WORKFLOW / 05/budget-guard [the run to bound — a phase, a loop, or the whole pipeline]
- 01
Define the done condition.
- 02
Set iteration, agent, or item caps.
- 03
Set token, tool-call, and/or wall-clock ceilings.
- 04
Name no-progress signatures and escalation triggers.
- 05
Monitor consumption and stop the instant any condition fires.
▸ operating envelope
Use it deliberately.
The shortest useful definition of where this skill helps—and where it should stay out of the way.
Use when
- Any unattended loop, fan-out, phase, or full pipeline is about to start.
- A run will spawn multiple agents or execute several repair rounds.
- The user needs a hard ceiling and a named escalation contract.
Do not use when
- The run has no measurable done condition.
- No one can state a cap, budget, no-progress rule, and escalation triggers.
- The intent is to raise limits silently whenever the run approaches them.
▸ output contract
What must be true when it stops.
Produces
- Five-condition stop declaration
- Actual iterations, agents, tokens, and time versus budget
- Done, capped, over-budget, or escalated exit reason
- Honest remaining-gap and user-decision report
Guarantees
- No unattended run begins without all five stop conditions.
- A budget is a ceiling, not a suggestion.
- A capped unfinished run returns an honest partial result.
- Ambiguity, destructive action, repeated no-progress, and imminent exhaustion escalate.
- Only the user can authorize a larger budget or changed scope.
Honest failure states
- capped — a hard count limit fired before completion
- over_budget — the token, tool-call, or time ceiling fired
- stalled — the declared no-progress condition fired
- escalated — a named user-owned trigger fired
▸ enforcement
Know which claims are executable.
Scripts are linked when this skill owns deterministic machinery. The remaining rules are explicit operating contracts and must not be marketed as hooks.
Procedural contract
This skill composes platform tools and verification evidence; it does not claim a dedicated guard script.
▸ install and invoke
One skill, three honest surfaces.
Claude Code plugin
AvailableInstall the full plugin, then invoke /budget-guard or let routing select it from context.
Codex plugin
Work in progressA work in progress on the codex-native-plugin branch — build it, start a new session, then invoke $autonomous-engineering:budget-guard.
▸ composes with