A pre-implementation checklist for exploring edge cases in gflow-cli features, where edge cases are unusual situations that can break normal behaviour. It organises possible problems by severity and by areas such as authentication, selectors, batch recovery, and file paths.

Use it to produce a severity-ranked scenario table, acceptance criteria, and suggested BDD tests for a proposed gflow-cli change.

It helps expose failure scenarios before coding begins, when they are easier to turn into requirements and tests. It also connects scenarios with known issues and planned work.

How ffroliva/gflow-cli configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ffroliva/gflow-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ffroliva/gflow-cli/develop/.claude/commands/gflow/scenario.md

Clone the repo

git clone --depth 1 https://github.com/ffroliva/gflow-cli

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ffroliva/gflow-cli/scenario/github.svg)](https://agentmods.dev/commands/ffroliva/gflow-cli/scenario)

Your own site

<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/scenario"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/scenario"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/scenario.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 301 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00067	$0.00301
Opus 5.5	$0.00027	$0.00120
Sonnet 5.5	$0.00013	$0.00060
Haiku 4.5	$0.00007	$0.00030

Measured 1mo ago against content hash 93775ae915ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

.claude/commands/gflow/scenario.md · 24 lines

What it actually says

`/gflow:scenario [feature description]`

Read skills/scenario/SKILL.md and follow its protocol now, passing $ARGUMENTS as the feature or change description.

Do not call Skill(skill="scenario") — the repo's skills/*/SKILL.md files are plain Markdown, not registered as Skill-tool-invocable (only .claude/commands/gflow/* are). Invoking it errors with Unknown skill: scenario. Read the file directly instead.

The skill at skills/scenario/SKILL.md covers 12 dimensions tuned to gflow-cli's known failure surfaces and outputs:

A severity-ranked scenario table (Critical / High / Medium / Low)
Must-cover acceptance criteria for the PLAN.md task
Suggested BDD Scenario: blocks for tests/features/
Cross-references to open KNOWN_ISSUES entries

Typical order: /gflow:predict → /gflow:scenario → PLAN.md task → /gflow:check → PR.

Changes

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.

1mo ago First seen · 24 lines · 67 tokens per session scan A 93775ae915ee

Subscribe to this mod's changes

scenario is a command published in the GitHub repository ffroliva/gflow-cli (337 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 301 once invoked, about $0.0003 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-08-30.

Claude Code Planning agentic ai-agents cli generative-ai google-flow

gflow-cli: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

`/gflow:scenario [feature description]`

What this file has done since we first saw it

Other commands, from other repositories

lint

proposal

proposal-lint

fix-issue

create-entity

hatch3r-workflow