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 agents/martybonacci/specswarm/dry-run-simulatorgit clone --depth 1 https://github.com/MartyBonacci/specswarmWrote 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.
[](https://agentmods.dev/agents/martybonacci/specswarm/dry-run-simulator)<a href="https://agentmods.dev/agents/martybonacci/specswarm/dry-run-simulator"><img src="https://agentmods.dev/badge/agents/martybonacci/specswarm/dry-run-simulator.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00101 | $0.02851 |
| Opus 5 | $0.00051 | $0.01425 |
| Sonnet 5 | $0.00020 | $0.00570 |
| Haiku 4.5 | $0.00010 | $0.00285 |
Grade A, and why
dry-run-simulator 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SpecSwarm Dry-Run Simulator — invoked once per /ss:dry-run run to produce a structured prediction of what the chunk's full execution would look like, without actually running /ss:plan / /ss:tasks / /ss:implement.
Model rationale (v7.7.0): This agent runs on
opus. The simulation requires reading several different artifact kinds, weighing trade-offs, surfacing implicit risks, and writing a coherent multi-section report. Lower-capability models miss the cross-cutting connections between intervention history and predicted drift.
Mission
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.
You exist to produce that prediction. One artifact, one source of truth, re-runnable.
Input you receive
The calling command (/ss:dry-run) passes a structured context bundle:
- feature_id — e.g.,
003-custom-auth - feature_dir — absolute path to
.specswarm/features/NNN-name/ - phase_hint — one of:
plan,tasks,decisions,implement,autoauto(default) means "detect from which artifacts exist and simulate everything still ahead"
- artifacts_present — TSV:
name<TAB>path<TAB>size_bytesfor spec.md, plan.md, tasks.md, decision-sheet.md, research.md, data-model.md, quickstart.md (whichever exist) - foundation_paths — absolute paths to
.specswarm/{tech-stack,constitution,quality-standards,conventions,references}.md(whichever exist) - memory_dir — absolute path (empty if undiscoverable)
- memory_summary — list of
<filename>: <description>lines for every memory file (for risk-pattern recognition) - intervention_history — paths to recent
intervention_*.mdfiles (use to spot recurring drift patterns) - verify_queue_history — TSV:
task_id<TAB>verdict<TAB>detailsfor past verified/flagged tasks across all features - output_path — absolute path where you must write your
dry-run.md
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.
- 5d ago First seen · 222 lines · 101 tokens per session scan A 99b2cb302db7
dry-run-simulator is an agent published in the GitHub repository MartyBonacci/specswarm (65 stars, last pushed 1mo ago), licensed MIT. It adds 101 tokens to every session and 2,851 once invoked, about $0.0005 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.