Borrowing it
Nothing to install: this file belongs to mort-lab/excel-mcp. 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/mort-lab/excel-mcp/main/.claude/commands/rapid-development/experimental/user-story-rapid.mdgit clone --depth 1 https://github.com/mort-lab/excel-mcpWrote 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/mort-lab/excel-mcp/user-story-rapid)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/user-story-rapid"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/user-story-rapid/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/mort-lab/excel-mcp/user-story-rapid"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/user-story-rapid.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.00735 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
user-story-rapid 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze User Story and Create Implementation Plan
User Story: $ARGUMENTS
Task: Create detailed implementation plan for separate backend and frontend projects based on the tech stack detailed in the user story
-
Parse user story:
- Extract: As a [user], I want [feature], so that [benefit]
- List explicit and implicit acceptance criteria
- Identify non-functional requirements (performance, security, UX)
- Define success metrics
-
Plan API contract first (backend/frontend agreement):
Endpoints: - GET /api/v1/{resources} - List with pagination - GET /api/v1/{resources}/{id} - Get single resource - POST /api/v1/{resources} - Create new - PUT /api/v1/{resources}/{id} - Update existing - DELETE /api/v1/{resources}/{id} - Delete DTOs: Request: {field validations} Response: {field types} Error: {standard error format} -
Backend implementation plan (Java project):
Package structure: com.company.feature/ ├── controller/ ├── service/ ├── repository/ ├── entity/ ├── dto/ ├── exception/ └── mapper/Implementation order:
- Entity with JPA annotations
- Repository interface
- DTOs with validation
- Mapper interface
- Service with business logic
- Controller with OpenAPI
- Exception handling
- Integration tests
-
Frontend implementation plan (React project):
src/features/{feature}/ ├── api/ # API client functions ├── components/ # UI components ├── hooks/ # Custom hooks ├── schemas/ # Zod validation ├── types/ # TypeScript types ├── __tests__/ # Component tests └── index.ts # Public exportsImplementation order:
- Zod schemas matching backend DTOs
- TypeScript types
- API client functions
- Custom hooks with TanStack Query
- UI components
- Forms with validation
- Error handling
- Component tests
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.
- 9d ago First seen · 101 lines · 0 tokens per session scan A 83257cf7ed86
user-story-rapid is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 735 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
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
ingest-dev
Ingest a URL, directory, or file into your knowledge base. remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference.
quarry
Manage your quarry knowledge base.
remember-dev
Remember inline text content in your knowledge base. remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference.
resume
Auto-detect and resume any interrupted Plan Cascade task. Detects mega-plan, hybrid-worktree, or hybrid-auto context and routes to the appropriate resume command.
scout
Scout vetted GitHub candidates for a thin shelf (or a stale entry's successor), deduped against the library, ending in /add-entry offers.