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-spec-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-spec-execute)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-spec-execute"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-spec-execute/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/prp-spec-execute"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-spec-execute.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.00178 |
| Opus 5.5 | $0.00000 | $0.00071 |
| Sonnet 5.5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
prp-spec-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 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.
This is a copy
100% identical to prp-spec-execute — 58 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Execute SPEC PRP
Implement a specification using an existing SPEC PRP.
PRP File: $ARGUMENTS
Execution Process
-
Understand Spec
- Current state analysis
- Desired state goals
- Task dependencies
-
ULTRATHINK
- Think hard before you execute the plan. Create a comprehensive plan addressing all requirements.
- Break down complex tasks into smaller, manageable steps using your todos tools.
- Use the TodoWrite tool to create and track your implementation plan.
- Identify implementation patterns from existing code to follow.
-
Execute Tasks
- Follow task order
- Run validation after each
- Fix failures before proceeding
-
Verify Transformation
- Confirm desired state achieved
- Run all validation gates
- Test integration
Progress through each objective systematically.
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.
- 2mo ago First seen · 30 lines · 0 tokens per session scan A 2f6ea6010acb
prp-spec-execute is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 178 tokens. A static security scan graded it A with 0 findings. It is 100% identical to prp-spec-execute, differing in 58 lines, and is treated as a copy.
Other commands, from other repositories
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
implement-plan
Implement the plan as specified, it is attached for your reference. Do NOT edit the plan file itself. Create todos for the plan as you work, starting with the first one. Don't stop until you have completed all the to-dos.
create
Command "create" from freema/mcp-jira-stdio, covering /jira:create, usage, examples and what happens.
project
Command "project" from getsentry/sentry-mcp, covering examples, list all projects in an org, filter by platform, view project details and open project in browser.
org
Command "org" from getsentry/sentry-mcp, covering examples, list organizations, view organization details, open in browser and json output.
trial
Command "trial" from getsentry/sentry-mcp, covering examples, list all trials for the current org, list trials for a specific org, start a seer trial and start a trial for a specific org.