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/prp-commands/prp-story-execute.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/prp-story-execute)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-story-execute"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-story-execute.svg" alt="Measured on agentmods" 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.00009 | $0.00494 |
| Opus 5 | $0.00005 | $0.00247 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
prp-story-execute 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Story PRP
PRP File: $ARGUMENTS
Mission
Execute a story/task PRP through sequential task completion with immediate validation.
Execution Philosophy: Complete one task, validate it, then move to the next. No task left behind.
Execution Process
1. Load Story PRP
- Read the specified story PRP file
- Understand the original story intent
- Review all context references
- Note validation commands for each task
2. Pre-Implementation Check
- Ultrathink about the story intent and task requirements
- Verify all referenced files exist
- Check that patterns mentioned are accessible
- Ensure development environment is ready
- Run any pre-requisite setup commands
3. Task-by-Task Implementation
For each task in the PRP:
a) Understand Task
- Read task requirements completely
- Review referenced patterns
- Check gotchas and constraints
b) Implement Task
- Follow the specified pattern
- Use the indicated naming conventions
- Apply the documented approach
- Handle edge cases mentioned
c) Validate Immediately
- Run the task's validation command
- If validation fails, fix and re-validate
- Don't proceed until current task passes
d) Mark Complete
- Update todo list to track progress
- Document any deviations if necessary
4. Full Validation
After all tasks complete:
- Run the validation gates from PRP
- Execute comprehensive test suite
- Verify all acceptance criteria met
5. Completion
- Work through completion checklist
- Ensure story requirements satisfied
- Move completed PRP to PRPs/completed/ create the folder if it does not exist
Execution Rules
Validation Gates: Each task must pass validation, iterate until passed Pattern Adherence: Follow existing patterns, don't create new ones No Shortcuts: Complete all validation steps
Failure Handling
When a task fails validation:
- Read the error message carefully
- Check the pattern reference again
- Validate it by investigating the codebase
- Fix and re-validate
- If stuck, check similar implementations
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.
- 8d ago First seen · 96 lines · 9 tokens per session scan A d6f8008bca9d
prp-story-execute is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 494 once invoked, about $0.0000 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-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.