Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MartyBonacci/specswarm/plugin install ss-statusWrote 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/martybonacci/specswarm/install)<a href="https://agentmods.dev/commands/martybonacci/specswarm/install"><img src="https://agentmods.dev/badge/commands/martybonacci/specswarm/install/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/martybonacci/specswarm/install"><img src="https://agentmods.dev/badge/commands/martybonacci/specswarm/install.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.00076 | $0.00392 |
| Opus 5.5 | $0.00030 | $0.00157 |
| Sonnet 5.5 | $0.00015 | $0.00078 |
| Haiku 4.5 | $0.00008 | $0.00039 |
Grade A, and why
install 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.
What it actually says
ss-status install
Run the installer, then explain what happened:
bash "${CLAUDE_PLUGIN_ROOT}/lib/install.sh" install
(Pass --refresh N through if the user gave it.)
Then tell the user, briefly:
- What they'll see: their statusline exactly as before, plus one extra line in SpecSwarm conduct projects —
🔨 building: <name> <elapsed>while a builder dispatch runs,💀 last build DIED (exit N)if the most recent run failed,✓ builders idle — safe to closeotherwise. In projects with no.specswarm/conduct/, nothing changes at all. - The point: "is it safe to shut down or close this session?" is now answered at a glance, in real time — no daemon, nothing to restart after a reboot.
- How it stays cheap: the wrapper re-renders their (potentially heavy) base statusline at most once per minute from cache, while the builder segment — a few file checks — refreshes every tick.
- Reversal:
/ss-status:uninstallrestores their exact previous configuration.
If the installer reported "wrapped existing statusline", confirm which script is now the base so the user knows nothing was lost.
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 First seen · 28 lines · 76 tokens per session scan A 7420f3b1060c
install is a command published in the GitHub repository MartyBonacci/specswarm (66 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 392 once invoked, about $0.0003 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.