statusline

Install

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.

agentmods

npx agentmods add commands/anshss/shiploop/statusline

Clone the repo

git clone --depth 1 https://github.com/anshss/shiploop

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/anshss/shiploop/statusline.svg)](https://agentmods.dev/commands/anshss/shiploop/statusline)

Your own site

<a href="https://agentmods.dev/commands/anshss/shiploop/statusline"><img src="https://agentmods.dev/badge/commands/anshss/shiploop/statusline.svg" alt="Measured on agentmods" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 736 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown No closer match found in the catalogue.

Token cost

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	$0.00027	$0.00736
Opus 5	$0.00014	$0.00368
Sonnet 5	$0.00005	$0.00147
Haiku 4.5	$0.00003	$0.00074

Measured today against content hash 5824321bf43b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 today.

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.

commands/statusline.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 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 · 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's cwd to 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 verbatim

Run status first on an install and show the operator what is currently in statusLine.command before wrapping it. If they already have something there, name it and confirm they want it wrapped rather than assuming.

Read the full file on GitHub · 65 lines

Changes

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.

today First seen · 65 lines · 27 tokens per session scan A 5824321bf43b

Subscribe to this mod's changes

statusline is a command published in the GitHub repository anshss/shiploop (6 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 736 once invoked, about $0.0001 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-04.

Autonomous Agents ai-agents claude-code claude-code-plugin developer-tools git-worktrees

scout-meta-review

Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.

Raven-Scout/scout-plugin · 61 tokens

scout-work

Interactive work session — walks through today's actionable items one at a time, presents a recommended action with draft content, and executes each one only with explicit approval. Runs in the current conversation (not as a background session).

Raven-Scout/scout-plugin · 47 tokens

polisade-review

Run a second-opinion quality review on a completed TASK via an independent clean-context subagent (self-review path only on opencode; the self flag is accepted for Claude/Codex parity and is a no-op here). Use when PM mentions "review TASK", "second opinion", "check my implementation", "codex review", "self-review"…

cryndoc/polisade-orchestrator · 99 tokens