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.
npx agentmods add skills/spacedock-dev/spacedock/fo-status-viewernpx skills add spacedock-dev/spacedock --skill fo-status-viewergit clone --depth 1 https://github.com/spacedock-dev/spacedockWrote 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/spacedock-dev/spacedock/fo-status-viewer)<a href="https://agentmods.dev/skills/spacedock-dev/spacedock/fo-status-viewer"><img src="https://agentmods.dev/badge/skills/spacedock-dev/spacedock/fo-status-viewer.svg" alt="Measured on agentmods" 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.00087 | $0.01101 |
| Opus 5 | $0.00044 | $0.00550 |
| Sonnet 5 | $0.00017 | $0.00220 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
fo-status-viewer 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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First Officer Status Viewer
Status Viewer
The ${SPACEDOCK_BIN:-spacedock} status launcher owns path resolution and mutation guards; skill instructions stay declarative and never reference a plugin-private script path.
Invoke it as:
${SPACEDOCK_BIN:-spacedock} status --workflow-dir {workflow_dir} [--page N|--limit N|--next-id|--next|--archived|--where ...|--boot|--validate|--resolve REF]
--boot— startup roll-up (mods, ID style, next-ID candidate, orphans, PR state, dispatchables). Incompatible with--next,--next-id,--archived,--where.--validate— run before trusting manually edited workflow state.--resolve REF— deterministic lookup by slug, exact stored ID, or sd-b32 address prefix;--rootrejects unqualified cross-workflow ambiguity rather than guessing.--next-id— preview the next-id candidate forsequentialandsd-b32(n/a forslug). Forsd-b32, pass--id-seed "{slug-or-title}"and optionally--id-actor "{actor-or-agent}"so creation context enters the candidate. To file a new entity, do NOT pair--next-idwith a hand-written file — usespacedock newunder the eagerly loaded«write.classify»contract, which mints the id and atomically writes the stamped entity in one call.--next-idis candidate-preview only.--where <field>=<value>— THE entity query. One clause per flag; repeat the flag to AND clauses (--where sprint=X --where 'sprint-readiness!=defer'). Two clauses in one string is an error, not an AND.field!=means non-empty,field=means empty. Unknown field names are a loud error listing the known fields. Known fields are this workflow's frontmatter keys plus the canonical set:id slug status title score source worktree pr started completed verdict mod-block archived issue. Neverfind/grepthe state dir — query it.--next— dispatchable entities.
The --set flag updates entity frontmatter fields:
--set {slug} field=valuesets a field--set {slug} field=clears a field--set {slug} startedorcompletedauto-fills a UTC ISO 8601 timestamp (skipped if already set)- a field with a schema
conventionallist (today:verdict,[PASSED REJECTED]) is closed on write — any other token is refused byte-clean;--forcebypasses. Clearing always passes. To supersede an entity, clearverdictand--archiveit.
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.
- 5d ago First seen · 59 lines · 87 tokens per session scan A 56623662c5ed
fo-status-viewer is a skill published in the GitHub repository spacedock-dev/spacedock (76 stars, last pushed 6d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,101 once invoked, about $0.0004 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
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave in isolated worktrees, collects discoveries, shares context between waves. Use when work decomposes into 3+ independent streams that can run simultaneously.
archon
Autonomous multi-session campaign agent. Decomposes large work into phases, delegates to sub-agents, reviews output, and maintains campaign state across context windows. Use for work that spans multiple sessions and needs persistent state, quality judgment, and strategic decomposition.
daemon
Continuous autonomous operation mode. Keeps campaigns running 24/7 by chaining Claude Code sessions via RemoteTrigger. Each session picks up from the campaign's continuation state, works until context runs low or the phase completes, then schedules the next session. Auto-stops on campaign completion or budget…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
setup
First-run experience for the harness. Three modes: Recommended (guided, 3 min), Full Tour (guided + skill walkthrough, 8 min), and Express (zero questions, 30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.
dashboard
Real-time harness observability dashboard. Reads campaigns, fleet sessions, telemetry, and pending queues to present a snapshot of harness state at a glance. Invoked by /dashboard, /do status, or phrases like "what's happening" and "show activity".