excel-mcp: Command for Claude Code

.claude/commands/prp-commands/prp-base-execute.md

prp-base-execute is a command for Claude Code from mort-lab/excel-mcp. It costs 0 tokens per session (557 once invoked), scanned A, original, MIT.

A command that reads a prepared implementation plan, called a PRP, and turns it into working code.

In plain words
What is it for?
Use it to carry out a PRP file, organize the implementation into tasks, inspect the codebase, and validate the resulting code.
Why use it?
It gathers the plan, codebase patterns, and requirements in one place so less information has to be guessed during implementation. It also checks the work through several validation stages.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; mentions subagents; names the TodoWrite tool.

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/prp-commands/prp-base-execute.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 prp-base-execute

README.md
[![agentmods](https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-base-execute/github.svg)](https://agentmods.dev/commands/mort-lab/excel-mcp/prp-base-execute)
Your own site
<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-base-execute"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-base-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.

agentmods 80×15 button for prp-base-execute

Your own site · 80×15
<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-base-execute"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-base-execute.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 557 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.00557
Opus 5.5 $0.00000 $0.00223
Sonnet 5.5 $0.00000 $0.00111
Haiku 4.5 $0.00000 $0.00056

Measured 2mo ago against content hash 55ffb5838b89, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

prp-base-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.

.claude/commands/prp-commands/prp-base-execute.md · 56 lines

How it starts

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

Execute BASE PRP

PRP File: $ARGUMENTS

Mission: One-Pass Implementation Success

PRPs enable working code on the first attempt through:

  • Context Completeness: Everything needed, nothing guessed
  • Progressive Validation: 4-level gates catch errors early
  • Pattern Consistency: Follow existing codebase approaches
  • Read PRPs/README.md to understand PRP concepts

Your Goal: Transform the PRP into working code that passes all validation gates.

Execution Process

  1. Load PRP

    • Read the specified PRP file completely
    • Absorb all context, patterns, requirements and gather codebase intelligence
    • Use the provided documentation references and file patterns, consume the right documentation before the appropriate todo/task
    • Trust the PRP's context and guidance - it's designed for one-pass success
    • If needed do additional codebase exploration and research as needed
  2. ULTRATHINK & Plan

    • Create comprehensive implementation plan following the PRP's task order
    • Break down into clear todos using TodoWrite tool
    • Use subagents for parallel work when beneficial (always create prp inspired prompts for subagents when used)
    • Follow the patterns referenced in the PRP
    • Use specific file paths, class names, and method signatures from PRP context
    • Never guess - always verify the codebase patterns and examples referenced in the PRP yourself
  3. Execute Implementation

    • Follow the PRP's Implementation Tasks sequence, add more detail as needed, especially when using subagents
    • Use the patterns and examples referenced in the PRP
    • Create files in locations specified by the desired codebase tree
    • Apply naming conventions from the task specifications and CLAUDE.md
  4. Progressive Validation

    Execute the level validation system from the PRP:

    • Level 1: Run syntax & style validation commands from PRP
    • Level 2: Execute unit test validation from PRP
    • Level 3: Run integration testing commands from PRP
    • Level 4: Execute specified validation from PRP

Read the full file on GitHub · 56 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. 2mo ago First seen · 56 lines · 0 tokens per session scan A 55ffb5838b89

Subscribe to this mod's changes

prp-base-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 557 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.