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 commands/martybonacci/specswarm/gogit clone --depth 1 https://github.com/MartyBonacci/specswarmWhat 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.00081 | $0.01199 |
| Opus 5 | $0.00041 | $0.00600 |
| Sonnet 5 | $0.00016 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
go 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 3d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecSwarm Go — the full ladder, ≤4 human touchpoints
North star: a small feature ships end-to-end with at most 4 human touchpoints — (1) this kickoff, (2) the assumptions review + batched decision sheet (back-to-back), (3) sighted gates on visual slices, (4) the ship blessing. Everything else runs itself. If you find yourself wanting to ask the user something outside those four, check the taste model and codebase precedent first (assume-with-provenance).
/ss:build is untouched and still works; /ss:go is the v7.17.0 ladder that includes the autonomous-loop phases (decisions, preflight, verify, retrospective) that build predates.
Step 1: Kickoff — write the go-loop state
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
PLUGIN_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
# shellcheck disable=SC1091
source "${PLUGIN_DIR}/lib/features-location.sh"
mkdir -p "${REPO_ROOT}/.specswarm"
# Refuse to stack loops
if [ -f "${REPO_ROOT}/.specswarm/go-loop.state" ] || [ -f "${REPO_ROOT}/.specswarm/build-loop.state" ]; then
echo "❌ A build/go loop is already active. Finish it or remove the state file first."
exit 1
fi
# Next feature number (mirrors /ss:build's convention)
get_features_dir "$REPO_ROOT"
LAST_NUM=$(list_features "$REPO_ROOT" 2>/dev/null | grep -oE '^[0-9]{3}' | sort -nr | head -1)
NEXT_NUM=$(printf '%03d' $(( ${LAST_NUM:-0} + 1 )))
jq -n \
--arg desc "<feature_description>" \
--arg num "$NEXT_NUM" \
--arg started "$(date -Iseconds)" \
'{
active: true,
feature_description: $desc,
feature_num: $num,
current_phase: "specify",
started_at: $started
}' > "${REPO_ROOT}/.specswarm/go-loop.state"
echo "🚀 /ss:go — feature ${NEXT_NUM}, ladder engaged (state: .specswarm/go-loop.state)"
Step 2: Run the ladder
Use the SlashCommand tool to execute: /ss:specify <feature_description>
From here the go-loop Stop hook (hooks/go-loop-hook.sh) drives phase advancement — after each phase's artifacts land, it blocks the stop and feeds the next phase's instructions. The phases, in order, with their pause semantics:
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.
- 3d ago First seen · 79 lines · 81 tokens per session scan A 076131692eef
go is a command published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,199 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.