dry-run

dry-run is a command for coding agents from MartyBonacci/specswarm. It costs 74 tokens per session (3,572 once invoked), scanned A, original, MIT.

A prediction command that describes what a SpecSwarm work chunk is expected to do without actually running it.

In plain words
What is it for?
Use it at the start of a work chunk or before shipping to create or refresh a structured prediction report.
Why use it?
It helps expose risks, missing information, wrong scope, and likely decisions before development begins.

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/dry-run
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.

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.

agentmods badge for dry-run

README.md
[![agentmods](https://agentmods.dev/badge/commands/martybonacci/specswarm/dry-run.svg)](https://agentmods.dev/commands/martybonacci/specswarm/dry-run)
Your own site
<a href="https://agentmods.dev/commands/martybonacci/specswarm/dry-run"><img src="https://agentmods.dev/badge/commands/martybonacci/specswarm/dry-run.svg" alt="Measured on agentmods" height="20"></a>
Per session 74 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,572 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.00074 $0.03572
Opus 5 $0.00037 $0.01786
Sonnet 5 $0.00015 $0.00714
Haiku 4.5 $0.00007 $0.00357

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

Security

Grade A, and why

dry-run 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.

plugins/ss/commands/dry-run.md · 347 lines

How it starts

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

SpecSwarm Dry-Run Prediction

Marty's most expensive operation is committing to a chunk that turns out to be the wrong shape. The dual-session mentor↔builder pattern existed partly to catch this BEFORE it shipped. With v7.x's automation, the equivalent safety rail is prediction: read what will be built, surface what's likely to go wrong, let Marty redirect before code lands.

Run this at chunk start (or any point before /ss:ship) to get a structured prediction. Re-runnable — the report rewrites on each invocation as more artifacts come into existence.

Phase 1: Resolve feature + phase scope

PLUGIN_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
# shellcheck disable=SC1091
source "${PLUGIN_DIR}/lib/features-location.sh"
# shellcheck disable=SC1091
source "${PLUGIN_DIR}/lib/intervention.sh"
# shellcheck disable=SC1091
[ -f "${PLUGIN_DIR}/lib/notify.sh" ] && source "${PLUGIN_DIR}/lib/notify.sh"

FEATURE_NUM=""
PHASE="auto"
HISTORY_LIMIT=20

while [ $# -gt 0 ]; do
  case "$1" in
    --phase)         PHASE="$2";         shift 2 ;;
    --history-limit) HISTORY_LIMIT="$2"; shift 2 ;;
    -h|--help)
      cat <<EOF
Usage: /ss:dry-run [FEATURE_NUM] [options]

Predict the chunk's full execution path without running it.

Options:
  --phase SCOPE      auto (default) | plan | tasks | decisions | implement
  --history-limit N  Past intervention/verify entries to feed the simulator (default 20)

Examples:
  /ss:dry-run
  /ss:dry-run 003
  /ss:dry-run 003 --phase implement
  /ss:dry-run --history-limit 50
EOF
      exit 0
      ;;
    *)
      if [ -z "$FEATURE_NUM" ]; then FEATURE_NUM="$1"; fi
      shift
      ;;
  esac
done

# Validate --phase
case "$PHASE" in
  auto|plan|tasks|decisions|implement) ;;
  *)
    echo "❌ Invalid --phase '$PHASE' (use: auto|plan|tasks|decisions|implement)" >&2
    exit 2
    ;;
esac

REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)

# Resolve feature (same cascade as /ss:decisions and /ss:retrospective)
if [ -z "$FEATURE_NUM" ]; then
  BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "")
  FEATURE_NUM=$(echo "$BRANCH" | grep -oE '^[0-9]{3}' || echo "")
fi
if [ -z "$FEATURE_NUM" ]; then
  get_features_dir "$REPO_ROOT"
  FEATURE_NUM=$(find "$FEATURES_DIR" -maxdepth 1 -type d -name '[0-9][0-9][0-9]-*' 2>/dev/null \
    | sort | tail -1 | xargs -n1 basename 2>/dev/null \
    | grep -oE '^[0-9]{3}' || echo "")
fi
if [ -z "$FEATURE_NUM" ]; then
  echo "❌ No feature number provided and no feature dirs found." >&2
  exit 2
fi
if ! find_feature_dir "$FEATURE_NUM" "$REPO_ROOT"; then
  echo "❌ Feature $FEATURE_NUM not found." >&2
  exit 2
fi
FEATURE_ID=$(basename "$FEATURE_DIR")

# Spec.md is mandatory — if it doesn't exist, /ss:specify hasn't run yet
SPEC_PATH="${FEATURE_DIR}/spec.md"
if [ ! -f "$SPEC_PATH" ]; then
  echo "❌ spec.md not found at $SPEC_PATH. Run /ss:specify first." >&2
  exit 2
fi

echo "🔮 Dry-run prediction for $FEATURE_ID"
echo "  feature_dir:    $FEATURE_DIR"
echo "  phase_scope:    $PHASE"
echo "  history_limit:  $HISTORY_LIMIT"
echo ""

Read the full file on GitHub · 347 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. 5d ago First seen · 347 lines · 74 tokens per session scan A 4bb94812b341

Subscribe to this mod's changes

dry-run is a command published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 3,572 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.