implement

A command that carries out every task listed in a feature's tasks.md implementation plan.

In plain words
What is it for?
Use it to find the relevant feature context and execute its planned implementation tasks.
Why use it?
It connects the written plan to the repository and branch where the feature will be built, reducing manual setup before coding.

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/implement
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 10,693 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.10693
Opus 5 $0.00007 $0.05346
Sonnet 5 $0.00003 $0.02139
Haiku 4.5 $0.00001 $0.01069

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

Security

Grade A, and why

implement 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/implement.md · 1,024 lines

How it starts

The opening of the file, as written. The whole thing — 1,024 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).

Outline

  1. Discover Feature Context:

    YOU MUST NOW discover the feature context using the Bash tool:

    a. Get repository root by executing:

    git rev-parse --show-toplevel 2>/dev/null || pwd
    

    Store the result as REPO_ROOT.

    b. Get current branch name by executing:

    git rev-parse --abbrev-ref HEAD 2>/dev/null
    

    Store the result as BRANCH.

    c. Extract feature number from branch name by executing:

    echo "$BRANCH" | grep -oE '^[0-9]{3}'
    

    Store the result as FEATURE_NUM.

    d. Initialize features directory and find feature:

    # Source features location helper
    SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
    PLUGIN_DIR="$(dirname "$SCRIPT_DIR")"
    source "$PLUGIN_DIR/lib/features-location.sh"
    
    # Initialize features directory
    get_features_dir "$REPO_ROOT"
    
    # If feature number is empty, find latest feature
    if [ -z "$FEATURE_NUM" ]; then
      FEATURE_NUM=$(list_features "$REPO_ROOT" | grep -oE '^[0-9]{3}' | sort -nr | head -1)
    fi
    
    # Find feature directory
    find_feature_dir "$FEATURE_NUM" "$REPO_ROOT"
    # FEATURE_DIR is now set by find_feature_dir
    

    f. Display to user:

    📁 Feature Context
    ✓ Repository: {REPO_ROOT}
    ✓ Branch: {BRANCH}
    ✓ Feature: {FEATURE_NUM}
    ✓ Directory: {FEATURE_DIR}
    

    g. Auto-verification readiness check (v7.11.0) — WARN, never HALT:

    The per-task verify-queue depends on (1) the tasks-completion-detector hook being wired into the plugin and (2) tasks.md using the canonical - [ ] T### checkbox format. Confirm both so you know the verification posture BEFORE running tasks. Run with Bash:

    PLUGIN_DIR_CHK="$(dirname "$SCRIPT_DIR")"
    HOOK_OK=false
    if grep -q "tasks-completion-detector" "${PLUGIN_DIR_CHK}/hooks/hooks.json" 2>/dev/null \
       && [ -f "${PLUGIN_DIR_CHK}/hooks/tasks-completion-detector.sh" ]; then
      HOOK_OK=true
    fi
    
    CANON_OK=false
    if [ -f "${FEATURE_DIR}/tasks.md" ] \
       && grep -qE '^[[:space:]]*-[[:space:]]+\[[ xX]\][[:space:]]+T[0-9]+' "${FEATURE_DIR}/tasks.md" 2>/dev/null; then
      CANON_OK=true
    fi
    
    if [ "$HOOK_OK" = true ] && [ "$CANON_OK" = true ]; then
      echo "✓ Auto-verification active: hook wired + tasks.md in canonical checkbox format."
    else
      echo "⚠️  Verify-queue auto-verification may be INACTIVE:"
      [ "$HOOK_OK" = false ] && echo "    • tasks-completion-detector hook not found in this plugin build."
      [ "$CANON_OK" = false ] && echo "    • tasks.md has no canonical '- [ ] T###' checkboxes (heading-only or empty)."
      echo "    Falling back to local-gates + whole-chunk spec-mentor dispatch at chunk end (Step 9b)."
      echo "    To re-enable per-task auto-verify, regenerate tasks.md via /ss:tasks (emits canonical checkboxes)."
    fi
    

    Do NOT halt — autonomous mode must still run. This check only makes the verification posture explicit so a silent gap is never mistaken for a clean pass.

Read the full file on GitHub · 1,024 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,024 lines · 14 tokens per session scan A e606b3b2264c

Subscribe to this mod's changes

implement 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 10,693 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.