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/modifygit 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.00014 | $0.07169 |
| Opus 5 | $0.00007 | $0.03585 |
| Sonnet 5 | $0.00003 | $0.01434 |
| Haiku 4.5 | $0.00001 | $0.00717 |
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.
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:
- Discover refactor context (find feature directory)
- Establish baseline metrics (complexity, duplication, coverage, maintainability)
- Create refactor specification documenting target, approach, and expected improvements
- Generate incremental refactoring tasks (each followed by test verification)
- Execute tasks: refactor step → run tests → verify identical results → repeat
- Measure final metrics and generate before/after comparison report
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.
- 2d ago First seen · 1,157 lines · 14 tokens per session scan A 09cccaf50eac
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.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.