agentmods.dev

user-story

user-story is a command for Claude Code from CrashBytes/claude-role-skills. It costs 6 tokens per session (347 once invoked), scanned A, original, Apache-2.0.

A user-story writing command turns a feature description into small development tasks from a user's point of view, each with acceptance criteria. It can also suggest priority, effort, dependencies, and technical notes.

In plain words
What is it for?
Use it to write stories such as “As a customer, I want to reset my password, so that I can regain access.” It is also for defining Given/When/Then checks and splitting large features into smaller end-to-end pieces.
Why use it?
It removes the need to break vague feature ideas into testable work by hand. It helps teams agree on what each task must achieve, including unusual cases and errors.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the role-based-skills plugin — 7 skills, 15 commands shipped together

not rated 8repo 8mo ago A scan 6 tokens original Apache-2.0

Good fit Use it to write stories such as “As a customer, I want to reset my password, so that I can regain access.” It is also for defining Given/When/Then checks and splitting large features into smaller end-to-end pieces.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/crashbytes/claude-role-skills/user-story
View source ↗ CrashBytes/claude-role-skills
Install

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.

Clone the repo
git clone --depth 1 https://github.com/CrashBytes/claude-role-skills

Made for: Claude Code.

Or install role-based-skills, the plugin that ships this one along with the rest of its 7 skills, 15 commands.

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.

agentmods badge for user-story

README.md
[![agentmods](https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/user-story/github.svg)](https://agentmods.dev/commands/crashbytes/claude-role-skills/user-story)
Your own site
<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/user-story"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/user-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.

agentmods 80×15 button for user-story

Your own site · 80×15
<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/user-story"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/user-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 347 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.00347
Opus 5.5 $0.00002 $0.00139
Sonnet 5.5 $0.00001 $0.00069
Haiku 4.5 $0.00001 $0.00035

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

Security

Grade A, and why

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

commands/user-story.md · 45 lines

What it actually says

Write User Stories

Generate well-structured user stories with acceptance criteria from a feature description.

Arguments

Feature to write stories for: $ARGUMENTS

Workflow

  1. Understand the feature

    • Parse the provided feature description
    • Identify the target user personas
    • Determine the business value

  2. Decompose into user stories

    • Apply INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
    • Format: "As a [persona], I want to [action], so that [benefit]"
    • Aim for stories that can be completed in 1-3 days
    • Break epics into vertical slices (each delivers end-to-end value)

  3. Write acceptance criteria for each story

    • Use Given/When/Then format
    • Cover the happy path, edge cases, and error states
    • Include non-functional requirements where relevant (performance, accessibility)
    • Each story should have 3-7 acceptance criteria

  4. Add story metadata

    • Suggested story points estimate (1, 2, 3, 5, 8, 13)
    • Priority recommendation (must-have, should-have, nice-to-have)
    • Dependencies on other stories
    • Technical notes for the development team

  5. Output

    • Numbered list of user stories
    • Acceptance criteria for each
    • Suggested implementation order
    • MVP subset recommendation (which stories deliver the core value)
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.

  1. 2mo ago First seen · 45 lines · 6 tokens per session scan A d6962f6e9bd0

Subscribe to this mod's changes

user-story is a command published in the GitHub repository CrashBytes/claude-role-skills (8 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 347 once invoked, about $0.0000 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-31.

Claude CodePlanningagent-skillsclaude-pluginclaude-skillsinfosec
Related

user-story compared with commands from other repositories

user-story next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
user-storyCrashBytes/claude-role-skillsCommand88mo agoApache-2.0A6Claude Code
launch-meta-campaignmarkifact/markifact-mcpCommand59yesterdayMITA36Claude Code, Cursor
negative-keyword-sweepmarkifact/markifact-mcpCommand59yesterdayMITA50Claude Code, Cursor
meetingssystemoperators/claude-pluginsCommand6todayMITA6Claude Code
notessystemoperators/claude-pluginsCommand6todayMITA6Claude Code
duck-offcentsandcode/rubber-duckCommand152mo agoMITA8Claude Code
triagenunoamorim99/agile-ledgerCommand120d agoMITA25Claude Code