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-spec-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-spec-create)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-spec-create"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-spec-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 | $0.00000 | $0.00614 |
| Opus 5 | $0.00000 | $0.00307 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
prp-spec-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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create SPEC PRP (Advanced)
Generate a comprehensive specification-driven PRP with clear transformation goals.
Specification: $ARGUMENTS
Analysis Process
-
Current State Assessment
- Map existing implementation
- Identify pain points
- Document technical debt
- Note integration points
-
Desired State Research
- Best practices for target state
- Implementation examples
- Migration strategies
- Risk assessment
- Dependency mapping
-
User Clarification
- Confirm transformation goals
- Priority of objectives
- Acceptable trade-offs
PRP Generation
Using /PRPs/templates/prp_spec.md:
State Documentation
current_state:
files: [list affected files]
behavior: [how it works now]
issues: [specific problems]
desired_state:
files: [expected structure]
behavior: [target functionality]
benefits: [improvements gained]
Hierarchical Objectives
- High-Level: Overall transformation goal
- Mid-Level: Major milestones
- Low-Level: Specific tasks with validation
Task Specification with information dense keywords
Information dense keywords:
- MIRROR: Mirror the state of existing code to be mirrored to another use case
- COPY: Copy the state of existing code to be copied to another use case
- ADD: Add new code to the codebase
- MODIFY: Modify existing code
- DELETE: Delete existing code
- RENAME: Rename existing code
- MOVE: Move existing code
- REPLACE: Replace existing code
- CREATE: Create new code
Example:
task_name:
action: MODIFY/CREATE
file: path/to/file
changes: |
- Specific modifications
- Implementation details
- With clear markers
validation:
- command: "test command"
- expect: "success criteria"
Implementation Strategy
- Identify dependencies
- Order tasks by priority and implementation order and dependencies logic
- Include rollback plans
- Progressive enhancement
User Interaction Points
- Objective Validation
- Review hierarchical breakdown
- Confirm priorities
- Identify missing pieces
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.
- 4d ago First seen · 122 lines · 0 tokens per session scan A 32683bd279bc
prp-spec-create is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 614 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.
quarry
Manage your quarry knowledge base.
remember-dev
Remember inline text content in your knowledge base.
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.