Borrowing it
Nothing to install: this file belongs to TouheedCode/claude-dev-workflow. 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/TouheedCode/claude-dev-workflow/master/.claude/commands/story.mdgit clone --depth 1 https://github.com/TouheedCode/claude-dev-workflowWrote 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/touheedcode/claude-dev-workflow/story)<a href="https://agentmods.dev/commands/touheedcode/claude-dev-workflow/story"><img src="https://agentmods.dev/badge/commands/touheedcode/claude-dev-workflow/story/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/touheedcode/claude-dev-workflow/story"><img src="https://agentmods.dev/badge/commands/touheedcode/claude-dev-workflow/story.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.00500 |
| Opus 5.5 | $0.00000 | $0.00200 |
| Sonnet 5.5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
story 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 2mo 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
/story — Generate User Story with BDD Scenarios
Arguments
$ARGUMENTS— Story ID and title (e.g., "US-001 User can create a new task")
Instructions
You are generating a User Story with BDD (Behavior-Driven Development) scenarios.
Story input: $ARGUMENTS
Step 1: Parse Input
Extract the story ID (e.g., US-001) and the story title from the arguments. If no ID is provided, ask the user for one.
Step 2: Find the PRD
Look for PRD files in docs/PRD-*.md. If multiple exist, ask the user which PRD this story belongs to. Read the PRD to understand the project context, features, and constraints.
Step 3: Generate the User Story
Create the story file at docs/stories/{story-ID}.md with this structure:
# {Story ID}: {Story Title}
## User Story
As a [type of user],
I want [action/goal],
So that [benefit/value].
## BDD Scenarios
### Scenario 1: {Happy path name}
**Given** [precondition]
**When** [action taken]
**Then** [expected outcome]
**And** [additional outcome if needed]
### Scenario 2: {Alternative path name}
**Given** [precondition]
**When** [action taken]
**Then** [expected outcome]
### Scenario 3: {Error/edge case name}
**Given** [precondition]
**When** [action taken]
**Then** [expected error handling]
## Acceptance Criteria
- [ ] {Criterion 1 — derived from scenarios}
- [ ] {Criterion 2}
- [ ] {Criterion 3}
## Technical Notes
Any implementation hints, API endpoints needed, data models involved, or dependencies on other stories.
## Dependencies
- PRD: {link to PRD file}
- Blocked by: {other story IDs, if any}
Step 4: Output
- Write the story to
docs/stories/{story-ID}.md - Print a summary: story ID, title, number of BDD scenarios, and file path
- Remind the user to run
/phased-plannext to create an implementation plan for this story
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.
- 2mo ago First seen · 69 lines · 0 tokens per session scan A 3880390c5b78
story is a command published in the GitHub repository TouheedCode/claude-dev-workflow (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 500 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-31.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
release
Release guide version (CHANGELOG + VERSION + README + landing sync + commit + push).
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.