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.
git clone --depth 1 https://github.com/frankxai/Starlight-Intelligence-SystemWrote 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/commands/frankxai/starlight-intelligence-system/yolo-abort)<a href="https://agentmods.dev/commands/frankxai/starlight-intelligence-system/yolo-abort"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/yolo-abort/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/commands/frankxai/starlight-intelligence-system/yolo-abort"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/yolo-abort.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.00031 | $0.00431 |
| Opus 5 | $0.00015 | $0.00216 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
yolo-abort 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
/yolo-abort — Immediate Halt
Kill switch. Use when /yolo is mid-action and you need to stop NOW. Cleaner than Ctrl-C because it saves partial state and runs the safe-rollback path.
Halt sequence
-
Halt in-flight action — if a Bash command is running, signal interrupt; if an Edit/Write is pending, drop the change.
-
Roll back in-flight git where reversible:
git restore --staged .if files were staged but not committedgit reset HEAD~1 --softif a commit just landed but no push happened- Do NOT force-push to undo an already-pushed commit (per spec §7.1 NEVER rules) — record as drift instead
-
Audit log finalize with abort flag:
{"event": "session-abort", "ts": "<ISO>", "reason": "<from user or 'unspecified'>", "in_flight_action": "<from last audit line>", "rollback_status": "<success | partial | drift-recorded>"} -
Drift event recording: if rollback was partial (e.g., commit was already pushed), write entry to
memory/_audit/yolo/_drift.jsonlso next session-open surfaces it. -
Operational vault note: append abort entry with timestamp + reason + rollback status. Strategic vault is NOT touched on abort — strategic-class decisions require a clean ship.
-
Phase-in counter NOT incremented on abort — aborted sessions don't count toward the 3-session phase-in unlock review.
Output
Final message: abort reason + rollback summary + drift flag count + path to audit log file + any operator follow-up actions.
Built on SIP · /yolo-abort · v1.0.0
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 · 39 lines · 31 tokens per session scan A b8de487543a9
yolo-abort is a command published in the GitHub repository frankxai/Starlight-Intelligence-System (8 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 431 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
dev
Developer tools — debug, commit, PR, code review, refactoring.
commit
Smart commit — preflight checks, convention detection, atomic commits. Delegates to git-master when available.
hotfix
Emergency fix workflow. Manages a fast, safe patching process for production errors.
fix
Quick bugfix commit. Use for fix bug, bugfix, patch, hotfix, correct error.
diagnose-synapse
Run a comprehensive diagnostic of the SYNAPSE context engine, comparing expected vs. actual pipeline state, including session performance analysis with exact timing data.
checkpoint
Full memory flush — refresh state.md, append to activity log, route any new decisions/insights, then commit and push.