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.
git clone --depth 1 https://github.com/Intai/story-flowWrote 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/intai/story-flow/execute-scenario)<a href="https://agentmods.dev/commands/intai/story-flow/execute-scenario"><img src="https://agentmods.dev/badge/commands/intai/story-flow/execute-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/intai/story-flow/execute-scenario"><img src="https://agentmods.dev/badge/commands/intai/story-flow/execute-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.00158 |
| Opus 5.5 | $0.00000 | $0.00063 |
| Sonnet 5.5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
execute-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 17d 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
Load skills in this order using the Skill tool:
- First:
story-flow:execute-bdd-scenario(plugin - general BDD framework) - Then:
execute-bdd-scenarioif it exists (project-level - overrides/extends the plugin) - Confirm which skills are loaded before continuing with the execution.
Execute BDD scenario $ARGUMENTS.
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.
- 17d ago Changed 3d1b7a0db4ad
- 23d ago Changed 1fe970c8e2bb
- 1mo ago Changed 6180f93aa1f8
- 1mo ago First seen · 13 lines · 0 tokens per session scan A d02520e3e7bd
execute-scenario is a command published in the GitHub repository Intai/story-flow (14 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 158 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
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
test
Run the app's microflow tests and verify it in the browser.
record
Record the browser while validating a flow, then judge it against a rubric.
naive-test
Drive the live app as a naive first-time user and report UX/behavior gaps before deploy.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.