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/buildgit 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.00016 | $0.08921 |
| Opus 5 | $0.00008 | $0.04460 |
| Sonnet 5 | $0.00003 | $0.01784 |
| Haiku 4.5 | $0.00002 | $0.00892 |
Grade A, and why
build 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 — 1,129 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).
Goal
Build a complete feature from natural language description through implementation and quality validation.
Purpose: Simplify feature development by orchestrating the complete workflow in a single command.
Workflow: Specify → Clarify → Plan → Tasks → Implement → (Validate) → Quality Analysis
User Experience:
- Single command instead of 7+ manual steps
- Interactive clarification (only pause point)
- Autonomous execution through implementation
- Quality validated automatically
- Ready for final merge with
/ss:ship
Pre-Flight Checks
Pre-Flight A: Parse Arguments
YOU MUST execute this block to parse the feature description and flags.
# Parse arguments
FEATURE_DESC=""
RUN_VALIDATE=false
QUALITY_GATE=80
BACKGROUND_MODE=false
NOTIFY_ON_COMPLETE=false
ORCHESTRATE_FLAG="" # "", "force", or "disable"
RUN_ANALYZE=false
RUN_CHECKLIST=false
QUICK_MODE=false
# Extract feature description (first non-flag argument)
for arg in $ARGUMENTS; do
if [ "${arg:0:2}" != "--" ] && [ -z "$FEATURE_DESC" ]; then
FEATURE_DESC="$arg"
elif [ "$arg" = "--validate" ]; then
RUN_VALIDATE=true
elif [ "$arg" = "--quality-gate" ]; then
shift
QUALITY_GATE="$1"
elif [ "$arg" = "--background" ]; then
BACKGROUND_MODE=true
elif [ "$arg" = "--notify" ]; then
NOTIFY_ON_COMPLETE=true
elif [ "$arg" = "--orchestrate" ]; then
ORCHESTRATE_FLAG="force"
elif [ "$arg" = "--no-orchestrate" ]; then
ORCHESTRATE_FLAG="disable"
elif [ "$arg" = "--analyze" ]; then
RUN_ANALYZE=true
elif [ "$arg" = "--checklist" ]; then
RUN_CHECKLIST=true
elif [ "$arg" = "--quick" ]; then
QUICK_MODE=true
fi
done
# Validate feature description
if [ -z "$FEATURE_DESC" ]; then
echo "❌ Error: Feature description required"
echo ""
echo "Usage: /ss:build \"feature description\" [options]"
echo ""
echo "Options:"
echo " --validate Run browser validation after implementation"
echo " --quality-gate N Set minimum quality score (default 80)"
echo " --orchestrate Force multi-agent parallel execution"
echo " --no-orchestrate Force sequential execution"
echo " --quick Quick build: skip clarification, auto micro-spec, execute immediately"
echo " --analyze Run cross-artifact consistency analysis"
echo " --checklist Generate requirements validation checklist"
echo " --background Run in background mode"
echo ""
echo "Examples:"
echo " /ss:build \"Add user authentication with email/password\""
echo " /ss:build \"Implement dark mode toggle\" --validate"
echo " /ss:build \"Add shopping cart\" --orchestrate"
echo " /ss:build \"Add dashboard\" --validate --quality-gate 85"
echo " /ss:build \"Add API\" --analyze --checklist"
exit 1
fi
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 · 1,129 lines · 16 tokens per session scan A 1346b0b46ed0
build 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 8,921 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.
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.