Borrowing it
Nothing to install: this file belongs to swarm-ai-research/swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/add_scenario.mdgit clone --depth 1 https://github.com/swarm-ai-research/swarmWrote 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/commands/swarm-ai-research/swarm/add_scenario)<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/add_scenario"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/add_scenario/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/add_scenario"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/add_scenario.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00254 |
| Opus 5 | $0.00000 | $0.00127 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
add_scenario 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 10d 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.
What it actually says
/add_scenario
Scaffold a new YAML scenario config with SWARM conventions — use when testing a new governance configuration or agent motif that uses existing domain infrastructure. Distinct from /add_domain (new task category requiring new data models and handlers) and /add_metric (new measurement on existing data).
Usage
/add_scenario <scenario_id> [motif]
Behavior
- Create
scenarios/<scenario_id>.yamlwith:
scenario_id,description,motifagentsminimal listsimulation(includeseed)governancesection (explicitly set the main toggles)rate_limitssectionpayoffsectionoutputssection that writes tologs/<scenario_id>_events.jsonlandlogs/<scenario_id>_metrics.csv
- Ensure the scenario is loadable:
python -c "from pathlib import Path; from swarm.scenarios.loader import load_scenario; load_scenario(Path('scenarios/<scenario_id>.yaml')); print('OK')"
- Add a short note to
docs/scenarios.mddescribing what mechanism the scenario isolates.
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.
- 10d ago First seen · 25 lines · 0 tokens per session scan A aaf9ce854682
add_scenario is a command published in the GitHub repository swarm-ai-research/swarm (42 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 254 tokens. 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
eval-skill
🚀 Enhanced with Local Validators: This command now uses local JavaScript validators for D1, D2, and D3 dimensions to significantly reduce token consumption while maintaining evaluation quality. Complex reasoning tasks (D4, D5, D6) continue to use LLM evaluation with local pre-analysis.
create-fixture
Create a new E2E test fixture skill.
tdd-green
Implement minimal code to make failing tests pass in TDD green phase.
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.