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/anshss/shiploopnpx agentmods add commands/anshss/shiploop/statuslineWrote 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/anshss/shiploop/statusline)<a href="https://agentmods.dev/commands/anshss/shiploop/statusline"><img src="https://agentmods.dev/badge/commands/anshss/shiploop/statusline/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/anshss/shiploop/statusline"><img src="https://agentmods.dev/badge/commands/anshss/shiploop/statusline.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.00027 | $0.00748 |
| Opus 5.5 | $0.00011 | $0.00299 |
| Sonnet 5.5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
statusline 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/shiploop:statusline
Adds a fleet segment to your Claude Code statusline:
⚙ 4/6 · #94 opus 22m
live workers (a worker is a trim, single-ticket session) · tickets answered this run · the oldest live worker (ticket, tier, elapsed). Silent when no fleet is running — in a session with no governor run it prints nothing at all.
$ARGUMENTS selects the action: install (default) · uninstall · status.
The one rule
Never clobber an existing statusLine.command. Plenty of people run ccusage, a git/model HUD, or
a hand-rolled script there. statusLine.command is a single string, so anything that just writes its
own value destroys theirs. The installer therefore records the entire previous statusLine object
verbatim into ~/.claude/shiploop-statusline.json and wraps it: the wrapper reads stdin once,
replays it to the recorded original, and appends our segment after it. Uninstall writes the recorded
object back byte for byte (including removing the key entirely when there was none before).
You do not implement any of that. scripts/govern/statusline-install.sh owns every settings edit.
Prerequisite
The segment reads governor/events.jsonl, which the governor only writes when GOVERN_EVENTS=1
(off by default). Say so if the operator has not set it — the statusline will otherwise be
permanently, correctly silent.
What to do
-
Locate the script. From the workspace root:
scripts/govern/statusline-install.sh. Prefer the workspace copy over any hub path — one installed copy serves every workspace, because the segment walks up from the session'scwdto find that workspace's event log. -
Run the action.
bash scripts/govern/statusline-install.sh status # what is wired up right now bash scripts/govern/statusline-install.sh install # record + wrap bash scripts/govern/statusline-install.sh uninstall # restore verbatimRun
statusfirst on an install and show the operator what is currently instatusLine.commandbefore wrapping it. If they already have something there, name it and confirm they want it wrapped rather than assuming.
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.
- 1mo ago Changed · +1 lines 59de52bed9ae
- 1mo ago First seen · 65 lines · 27 tokens per session scan A 5824321bf43b
statusline is a command published in the GitHub repository anshss/shiploop (9 stars, last pushed 12d ago), licensed Apache-2.0. It adds 27 tokens to every session and 748 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-09-04.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
quickstart
Interactive onboarding guide — set up credentials, connect to orq.ai, and learn every command and skill.
focus
You are an ADHD focus assistant. Help the user commit to ONE task and block mental distractions.
stuck
You are an ADHD-friendly unblocking assistant. Help users get unstuck when they don't know what to do.
r
Resume the last handoff and carry on with the outstanding work.