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 skills/bang9/ai-tools/whip-simulatenpx skills add bang9/ai-tools --skill whip-simulategit clone --depth 1 https://github.com/bang9/ai-toolsWrote 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/skills/bang9/ai-tools/whip-simulate)<a href="https://agentmods.dev/skills/bang9/ai-tools/whip-simulate"><img src="https://agentmods.dev/badge/skills/bang9/ai-tools/whip-simulate.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.00040 | $0.01523 |
| Opus 5 | $0.00020 | $0.00762 |
| Sonnet 5 | $0.00008 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
whip-simulate 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use $whip-simulate <scenario> to run multi-agent simulations from a user-provided scenario. Concretize the scenario into test cases, execute each run in whip mode or agent mode, and analyze output patterns for consistency.
You are a simulation lead — you turn vague "run it a few times" ideas into controlled experiments with disciplined inputs and comparable outputs. You care about explicit output contracts, honest analysis, and clean evidence. If the setup is fuzzy, tighten it before spending runs.
Input
Extract from $ARGUMENTS:
- Scenario: what to simulate, compare, or verify
--runs N: number of simulation runs (default: 5)--agent: use inline mode (see Execution Mode below)
Execution Mode (mutually exclusive)
$ARGUMENTS determines which dispatch mode this skill uses. The two modes are mutually exclusive:
| Mode | Activates when | Dispatch mechanism |
|---|---|---|
| Tracked (default) | --agent is absent from $ARGUMENTS |
$whip-start Team Flow — IRC, workspace, polling |
| Inline | --agent is present in $ARGUMENTS |
Agent tool directly — no whip, no IRC, no lifecycle |
Strict rules:
- No
--agentin arguments → tracked mode. No exceptions, no inference. --agentin arguments → inline mode.$whip-start, IRC, and lifecycle steps are all skipped.--backendspecification (e.g., user says "use codex") → implies tracked mode. Backend selection is a whip concept and is incompatible with--agent.- Do NOT infer
--agentfrom task simplicity, speed preference, or any other heuristic. The flag must be explicitly present in the user's input.
If running inside an active whip workspace, use whip workspace view <workspace-name> to get the worktree path for reading code artifacts referenced in the scenario. In tracked mode, simulation tasks go in the global workspace (ephemeral — do not pollute the active workspace).
Workflow
1. Concretize
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 159 lines · 40 tokens per session scan A fee99fd59548
whip-simulate is a skill published in the GitHub repository bang9/ai-tools (10 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,523 once invoked, about $0.0002 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-31.
Other skills, from other repositories
backlog-technical-project-manager
Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…
kanban-tui
Comprehensive kanban board and task management via ktui CLI. Use for project tracking, todo lists, task dependencies, workflow automation, and board management. Activates when user mentions boards, tasks, kanban, or project management. If the ktui command is not available, but uv is available utilize uvx kanban-tui…
verify-frontend-change
Verify a frontend change actually works in the GSD Task Manager app before trusting it. Drives the running app browser-first — seeds IndexedDB, busts the PWA service-worker cache, then observes real behavior plus console/network errors — and codifies regression-worthy behavior as a Playwright spec. Use whenever you've…
verify-frontend-change
Verify a frontend change actually works in the GSD Task Manager app before trusting it. Drives the running app browser-first — seeds IndexedDB, busts the PWA service-worker cache, then observes real behavior plus console/network errors — and codifies regression-worthy behavior as a Playwright spec. Use whenever you've…
branch-preflight
Sanity-check the working tree before starting plan execution or new branch work. Catches inherited damage that silently breaks verification later — merge conflict markers committed to tracked files, outstanding stash entries that may bleed into your work, uncommitted changes you may not realize you have. Runs in 1…
reviewable-pr-slicing
Convert an approved technical plan into a sequence of small, reviewable PRs with clear phase boundaries, validation gates, and PR descriptions. Use for multi-step refactors, workflow changes, security-remediation tranches, documentation-plus-code rollouts, or any change that is too risky or noisy for one PR.