modify

A command for changing, refactoring, deprecating, or analysing code according to selected modes. Refactoring means improving code structure while keeping its behaviour the same.

In plain words
What is it for?
It is for applying a requested modification, running a metrics-based behaviour-preserving refactor, marking work for deprecation, or analysing without changing it.
Why use it?
It gives different kinds of code changes a defined workflow, including measurements and tests when the refactoring mode is used.

Command

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/modify
Clone the repo
git clone --depth 1 https://github.com/MartyBonacci/specswarm
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,169 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.00014 $0.07169
Opus 5 $0.00007 $0.03585
Sonnet 5 $0.00003 $0.01434
Haiku 4.5 $0.00001 $0.00717

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

Security

Grade A, and why

modify 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 2d 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/modify.md · 1,157 lines

How it starts

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

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Flag Parsing

# Parse flags from arguments
MODIFY_DESC=""
REFACTOR_MODE=false
DEPRECATE_MODE=false
ANALYZE_ONLY=false

for arg in $ARGUMENTS; do
  if [ "${arg:0:2}" != "--" ] && [ -z "$MODIFY_DESC" ]; then
    MODIFY_DESC="$arg"
  elif [ "$arg" = "--refactor" ]; then
    REFACTOR_MODE=true
  elif [ "$arg" = "--deprecate" ]; then
    DEPRECATE_MODE=true
  elif [ "$arg" = "--analyze-only" ]; then
    ANALYZE_ONLY=true
  fi
done

Mode Routing

IF --refactor flag is set, execute metrics-driven behavior-preserving refactoring workflow:

if [ "$REFACTOR_MODE" = true ]; then
  echo "♻️  SpecSwarm Modify --refactor"
  echo "══════════════════════════════════════════"
  echo ""
  echo "Mode: Behavior-Preserving Quality Improvement"
  echo ""
  echo "This workflow will:"
  echo "  1. Establish baseline metrics (complexity, duplication, coverage)"
  echo "  2. Create refactoring specification"
  echo "  3. Execute incremental refactoring steps"
  echo "  4. Verify behavior preservation after each step (test suite)"
  echo "  5. Measure final metrics and compare improvement"
  echo ""
  echo "Key principles:"
  echo "  • No functional changes - behavior must be identical"
  echo "  • Metrics-driven - quantify improvements"
  echo "  • Incremental - small, safe refactoring steps"
  echo "  • Testable - verify identical behavior before/after"
  echo ""
fi

IF REFACTOR_MODE = true: Execute the refactoring workflow:

  1. Discover refactor context (find feature directory)
  2. Establish baseline metrics (complexity, duplication, coverage, maintainability)
  3. Create refactor specification documenting target, approach, and expected improvements
  4. Generate incremental refactoring tasks (each followed by test verification)
  5. Execute tasks: refactor step → run tests → verify identical results → repeat
  6. Measure final metrics and generate before/after comparison report

Read the full file on GitHub · 1,157 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. 2d ago First seen · 1,157 lines · 14 tokens per session scan A 09cccaf50eac

Subscribe to this mod's changes

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