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/triage-failed-scenarios)<a href="https://agentmods.dev/commands/intai/story-flow/triage-failed-scenarios"><img src="https://agentmods.dev/badge/commands/intai/story-flow/triage-failed-scenarios/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/triage-failed-scenarios"><img src="https://agentmods.dev/badge/commands/intai/story-flow/triage-failed-scenarios.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.00024 | $0.00310 |
| Opus 5.5 | $0.00010 | $0.00124 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
triage-failed-scenarios 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 yesterday.
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
Execute the Playwright specs: npx playwright test $ARGUMENTS.
For each failed scenario, decide the cause against the current code and its story (the ticket ID in the feature file, or in its git log), fetched with the project's story tracker MCP tools when available:
- Behaviour removed: delete the scenario from both the feature file and the Playwright spec file.
- Behaviour changed intentionally: update the feature file steps, then re-record.
- Spec stale (locators, timing): re-record.
- App behaviour is wrong: do not change the scenario; report it as a defect.
Re-record with /story-flow:execute-scenario <ID> @<feature file> --record, at the failing project's form factor.
Confirm each re-recorded scenario passes on its failing project: npx playwright test <spec file> --project=<project> --grep "<ID>:".
If it still fails, triage it again rather than re-recording a second time.
Then summarise each failure's cause, action and scenario author (git blame on its lines in the feature file), plus any flaky passes.
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.
- yesterday Changed 98587b76a1e7
- 10d ago First seen · 19 lines · 24 tokens per session scan A f1e963a60c51
triage-failed-scenarios is a command published in the GitHub repository Intai/story-flow (14 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 310 once invoked, about $0.0001 per session on Opus 5.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-10-07.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
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…
qawolfCliRunResults.template
How to use what qawolf run get --run-id --json returns, and how to read the Playwright trace it links to.
debug
Deep-dive artifact analysis for diagnosing E2E test failures.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.