A command that turns a feature description into a user story with acceptance criteria. Acceptance criteria are clear conditions for deciding whether the feature works.

It helps define a user's role, desired action, expected benefit, and test scenarios such as normal use and invalid input.

It turns broad requirements into a form developers and testers can discuss, estimate, and verify.

user-story — Command for Claude Code by thapaliyabikendra

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/thapaliyabikendra/ai-artifacts

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/thapaliyabikendra/ai-artifacts/user-story/github.svg)](https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/user-story)

Your own site

<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/user-story"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/user-story"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/user-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 933 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.00012	$0.00933
Opus 5	$0.00006	$0.00466
Sonnet 5	$0.00002	$0.00187
Haiku 4.5	$0.00001	$0.00093

Measured 10d ago against content hash 1ba667b7086c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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/ba/user-story.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate User Story

Feature: $ARGUMENTS.feature Primary role: $ARGUMENTS.role

Instructions

Step 1: Gather Context

If feature exists in docs/features/, read existing requirements
Check docs/domain/entities/ for related entities
Review docs/domain/permissions.md for applicable permissions
Identify related user stories if any exist

Step 2: Generate User Story

Use INVEST criteria:

Independent: Can be developed separately
Negotiable: Details can be discussed
Valuable: Delivers user value
Estimable: Can be sized
Small: Fits in a sprint
Testable: Has clear acceptance criteria

# US-[XXX]: [Feature Title]

## Story

**As a** [role],
**I want to** [action/capability],
**So that** [benefit/value].

## Context

[Brief background on why this feature is needed and how it fits into the system]

## Acceptance Criteria

### AC-1: [Happy Path Scenario]
```gherkin
Given [initial context]
  And [additional context if needed]
When [action is performed]
Then [expected outcome]
  And [additional outcomes]

AC-2: [Validation Scenario]

Given [context with invalid input]
When [action is attempted]
Then [validation error is shown]
  And [operation is not completed]

AC-3: [Authorization Scenario]

Given a user without [required permission]
When they attempt to [action]
Then access is denied with 403 Forbidden

AC-4: [Edge Case Scenario]

Given [edge condition]
When [action is performed]
Then [graceful handling occurs]

Business Rules

ID	Rule	Condition	Action
BR-001	[Rule name]	[When condition]	[Then action]
BR-002	[Rule name]	[When condition]	[Then action]

Data Requirements

Field	Type	Required	Validation	Notes
[field]	[type]	Yes/No	[rules]	[notes]

UI/UX Notes

[Key interaction patterns]
[Form layout considerations]
[Error message display]

Dependencies

Requires: [List prerequisite stories]
Blocks: [List stories that depend on this]
Related: [Associated stories]

Technical Notes

[API endpoint suggestions]
[Database considerations]
[Integration points]

Priority & Sizing

Priority: Must Have | Should Have | Could Have
Effort: S (1-2d) | M (3-5d) | L (1-2w) | XL (2+w)
Risk: Low | Medium | High

Open Questions

[Question 1]
[Question 2]

Read the full file on GitHub · 152 lines

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.

10d ago First seen · 152 lines · 12 tokens per session scan A 1ba667b7086c

Subscribe to this mod's changes

user-story is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 933 once invoked, about $0.0001 per session on Opus 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.

Planning

user-story