status

A command for checking background SpecSwarm sessions, which are longer-running software workflows such as building, fixing, or releasing changes. It can list active or recent sessions and optionally print detailed or JSON-formatted output.

In plain words
What is it for?
Use it to view all session statuses or inspect one session by ID, with optional verbose and machine-readable JSON output.
Why use it?
It lets you check progress without interrupting a workflow running in the background. It also reports when no sessions exist and shows where session data is stored.

Command

Part of the ss plugin — 10 skills, 34 commands, 6 agents, 4 hooks shipped together

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/martybonacci/specswarm/status
Clone the repo
git clone --depth 1 https://github.com/MartyBonacci/specswarm

Or install ss, the plugin that ships this one along with the rest of its 10 skills, 34 commands, 6 agents, 4 hooks.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,758 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.01758
Opus 5 $0.00008 $0.00879
Sonnet 5 $0.00003 $0.00352
Haiku 4.5 $0.00002 $0.00176

Measured 3d ago against content hash 6e27fe42a5b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/ss/commands/status.md · 233 lines

How it starts

The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

Goal

Check the status of background SpecSwarm sessions (build, fix, release) or list all active/recent sessions.

Purpose: Track progress of background workflows without interrupting their execution.


Implementation

#!/bin/bash

echo "📊 SpecSwarm Session Status"
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo ""

# Get repository root
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
SESSIONS_DIR="${REPO_ROOT}/.specswarm/sessions"

# Parse arguments
SESSION_ID=""
VERBOSE=false
JSON_OUTPUT=false

for arg in $ARGUMENTS; do
  if [ "${arg:0:2}" != "--" ] && [ -z "$SESSION_ID" ]; then
    SESSION_ID="$arg"
  elif [ "$arg" = "--verbose" ]; then
    VERBOSE=true
  elif [ "$arg" = "--json" ]; then
    JSON_OUTPUT=true
  fi
done

# Check if sessions directory exists
if [ ! -d "$SESSIONS_DIR" ]; then
  echo "ℹ️  No sessions found"
  echo ""
  echo "Start a background session with:"
  echo "  /ss:build \"feature\" --background"
  echo "  /ss:fix \"bug\" --background"
  echo "  /ss:release --background"
  exit 0
fi

# Function to display session status
display_session() {
  local session_file=$1
  local session_name=$(basename "$session_file" .json)

  if [ ! -f "$session_file" ]; then
    echo "❌ Session not found: $session_name"
    return 1
  fi

  # Parse session JSON
  if command -v jq &> /dev/null; then
    local session_type=$(jq -r '.type // "build"' "$session_file")
    # v7.17.0 fix: build.md writes .active (bool), not .status — fall back so
    # active builds show "running" instead of "unknown".
    local status=$(jq -r 'if .status then .status elif .active == true then "running" elif .active == false then "completed" else "unknown" end' "$session_file")
    local started_at=$(jq -r '.started_at // "unknown"' "$session_file")
    local current_phase=$(jq -r '.current_phase // "unknown"' "$session_file")
    local description=$(jq -r '.feature_description // .bug_description // "N/A"' "$session_file")
    local quality_score=$(jq -r '.quality_score // "N/A"' "$session_file")

    # Determine status emoji (use status field, not active flag)
    local status_emoji="⏳"
    if [ "$status" = "completed" ]; then
      status_emoji="✅"
    elif [ "$status" = "failed" ]; then
      status_emoji="❌"
    elif [ "$status" = "running" ]; then
      status_emoji="🔄"
    fi

    if [ "$JSON_OUTPUT" = true ]; then
      cat "$session_file"
      return 0
    fi

    echo "┌─────────────────────────────────────────────"
    echo "│ Session: $session_name"
    echo "├─────────────────────────────────────────────"
    echo "│ Status:      $status_emoji $status"
    echo "│ Type:        $session_type"
    echo "│ Description: $description"
    echo "│ Started:     $started_at"
    echo "│ Phase:       $current_phase"

    if [ "$VERBOSE" = true ]; then
      local phases_complete=$(jq -r '.phases_complete // [] | join(", ")' "$session_file")
      local quality_threshold=$(jq -r '.quality_threshold // 80' "$session_file")
      local run_validate=$(jq -r '.run_validate // false' "$session_file")

      echo "├─────────────────────────────────────────────"
      echo "│ Phases Complete: ${phases_complete:-none}"
      echo "│ Quality Score:   $quality_score"
      echo "│ Quality Gate:    $quality_threshold%"
      echo "│ Validation:      $run_validate"
    fi

    echo "└─────────────────────────────────────────────"
    echo ""
  else
    # Fallback without jq
    echo "Session: $session_name"
    cat "$session_file"
    echo ""
  fi
}

# If specific session requested
if [ -n "$SESSION_ID" ]; then
  session_file="${SESSIONS_DIR}/${SESSION_ID}.json"

  # Also check build-loop.state for active builds
  if [ ! -f "$session_file" ] && [ -f "${REPO_ROOT}/.specswarm/build-loop.state" ]; then
    active_session=$(jq -r '.session_id' "${REPO_ROOT}/.specswarm/build-loop.state" 2>/dev/null)
    if [ "$active_session" = "$SESSION_ID" ]; then
      session_file="${REPO_ROOT}/.specswarm/build-loop.state"
    fi
  fi

  display_session "$session_file"
  exit 0
fi

# List all sessions
echo "📋 All Sessions"
echo ""

# Count sessions
session_count=$(find "$SESSIONS_DIR" -name "*.json" 2>/dev/null | wc -l)

if [ "$session_count" -eq 0 ]; then
  echo "ℹ️  No sessions found"
  exit 0
fi

# Display recent sessions (last 10)
echo "Recent sessions (newest first):"
echo ""

find "$SESSIONS_DIR" -name "*.json" -type f -printf '%T@ %p\n' 2>/dev/null | \
  sort -rn | head -10 | cut -d' ' -f2- | \
  while read session_file; do
    display_session "$session_file"
  done

# Check for active build
if [ -f "${REPO_ROOT}/.specswarm/build-loop.state" ]; then
  active=$(jq -r '.active' "${REPO_ROOT}/.specswarm/build-loop.state" 2>/dev/null)
  if [ "$active" = "true" ]; then
    echo ""
    echo "🔄 Active Build Detected"
    echo "━━━━━━━━━━━━━━━━━━━━━━━"
    display_session "${REPO_ROOT}/.specswarm/build-loop.state"
  fi
fi

echo ""
echo "Commands:"
echo "  /ss:status <session-id>           View specific session"
echo "  /ss:status <session-id> --verbose Full details"
echo "  /ss:status --json                 JSON output"

Read the full file on GitHub · 233 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.

  1. 3d ago First seen · 233 lines · 16 tokens per session scan A 6e27fe42a5b7

Subscribe to this mod's changes

status is a command published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,758 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-08-30.