excel-mcp: Command for Claude Code

.claude/commands/rapid-development/experimental/user-story-rapid.md

user-story-rapid is a command for Claude Code from mort-lab/excel-mcp. It costs 0 tokens per session (735 once invoked), scanned A, original, MIT.

A command that turns a user story—a short description of a user's need—into an implementation plan for separate Java backend and frontend projects.

In plain words
What is it for?
Use it to plan endpoints, request and response data, validation, errors, database entities, repositories, services, and frontend-backend integration.
Why use it?
It exposes acceptance criteria, technical requirements, and the API agreement both projects need before development begins.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is mort-lab/excel-mcp's own configuration. It tells Claude Code how to work on excel-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything excel-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/mort-lab/excel-mcp/main/.claude/commands/rapid-development/experimental/user-story-rapid.md
Clone the repo
git clone --depth 1 https://github.com/mort-lab/excel-mcp

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.

agentmods badge for user-story-rapid

README.md
[![agentmods](https://agentmods.dev/badge/commands/mort-lab/excel-mcp/user-story-rapid/github.svg)](https://agentmods.dev/commands/mort-lab/excel-mcp/user-story-rapid)
Your own site
<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.

agentmods 80×15 button for user-story-rapid

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 735 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.00000 $0.00735
Opus 5 $0.00000 $0.00367
Sonnet 5 $0.00000 $0.00147
Haiku 4.5 $0.00000 $0.00073

Measured 9d ago against content hash 83257cf7ed86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

.claude/commands/rapid-development/experimental/user-story-rapid.md · 101 lines

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

  1. 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
  2. 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}
    
  3. Backend implementation plan (Java project):

    Package structure:
    com.company.feature/
    ├── controller/
    ├── service/
    ├── repository/
    ├── entity/
    ├── dto/
    ├── exception/
    └── mapper/
    

    Implementation order:

    1. Entity with JPA annotations
    2. Repository interface
    3. DTOs with validation
    4. Mapper interface
    5. Service with business logic
    6. Controller with OpenAPI
    7. Exception handling
    8. Integration tests
  4. 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 exports
    

    Implementation order:

    1. Zod schemas matching backend DTOs
    2. TypeScript types
    3. API client functions
    4. Custom hooks with TanStack Query
    5. UI components
    6. Forms with validation
    7. Error handling
    8. Component tests

Read the full file on GitHub · 101 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.

  1. 9d ago First seen · 101 lines · 0 tokens per session scan A 83257cf7ed86

Subscribe to this mod's changes

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.