Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/mort-lab/excel-mcp/prp-planning-creategit 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-planning-create)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-planning-create"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-planning-create.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.00000 | $0.00713 |
| Opus 5 | $0.00000 | $0.00357 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
prp-planning-create 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 5d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PLANNING PRP (Advanced)
Transform rough ideas into comprehensive PRDs with rich visual documentation.
Idea: $ARGUMENTS
Discovery Process
-
Concept Expansion
- Break down the core idea
- Define success criteria
- Map to business goals if provided
-
Market & Technical Research
- Do deep web search for the following:
- Market analysis
- Competitor analysis
- Technical feasibility study
- Best practice examples
- Integration possibilities
- Do deep web search for the following:
-
User Research & Clarification
- Ask user for the following if not provided:
- Target user personas?
- Key pain points?
- Success metrics?
- Constraints/requirements?
PRD Generation
Using /PRPs/templates/prp_planning_base.md:
Visual Documentation Plan
diagrams_needed:
user_flows:
- Happy path journey
- Error scenarios
- Edge cases
architecture:
- System components
- Data flow
- Integration points
sequences:
- API interactions
- Event flows
- State changes
data_models:
- Entity relationships
- Schema design
- State machines
Research Integration
- Market Analysis: Include findings in PRD
- Technical Options: Compare approaches
- Risk Assessment: With mitigation strategies
- Success Metrics: Specific, measurable
User Story Development
## Epic: [High-level feature]
### Story 1: [User need]
**As a** [user type]
**I want** [capability]
**So that** [benefit]
**Acceptance Criteria:**
- [ ] Specific behavior
- [ ] Edge case handling
- [ ] Performance requirement
**Technical Notes:**
- Implementation approach
- API implications
- Data requirements
Implementation Strategy
- Phases with dependencies (no dates)
- Priority ordering
- MVP vs enhanced features
- Technical prerequisites
User Interaction Points
-
Idea Validation
- Confirm understanding
- Clarify ambiguities
- Set boundaries
-
Research Review
- Share findings
- Validate assumptions
- Adjust direction
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.
- 5d ago First seen · 142 lines · 0 tokens per session scan A 689bf3ae2606
prp-planning-create is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 713 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.
instructions
Use the instructions command to print the CLI playbook and current server inventory for AI agents using a running 1MCP serve instance.
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.