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-core-executegit 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-core-execute)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/prp-core-execute"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/prp-core-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 | $0.00008 | $0.00343 |
| Opus 5 | $0.00004 | $0.00171 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
prp-core-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 3d 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.
What it actually says
Execute Feature PRP
PRP File: $ARGUMENTS
Instructions
- Ingest the PRP file completely
- Think hard about the implementation approach
- Execute every task in the STEP-BY-STEP TASKS section sequentially
- Validate after each task using the task's validation command
- If validation fails, fix and re-validate before proceeding
- Run full validation suite from the PRP when all tasks complete
- Critical: Don't stop until the entire plan is fulfilled and all validation passes
- Use TodoWrite to track progress through tasks
- Trust the PRP's strategic direction, but verify tactical details (imports, paths, names)
- If the PRP has errors in details, fix them and note in report
Success Criteria
- ✓ Every task completed
- ✓ All validation commands pass
- ✓ Acceptance criteria met
Completion
Once all validation passes:
mkdir -p .claude/PRPs/features/completed
mv .claude/PRPs/features/{prp-file}.md .claude/PRPs/features/completed/
Report
After completion:
Summary:
- Feature: {name}
- Tasks completed: {count}
- Files created/modified: {list}
Validation:
✓ Linting: Passed
✓ Type checking: Passed
✓ Tests: X/X passed
Adjustments (if any):
- Note any PRP details that were incorrect and how you fixed them
Files Changed:
git diff --stat
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.
- 3d ago First seen · 60 lines · 8 tokens per session scan A fb8888da4483
prp-core-execute is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 26d ago), licensed MIT. It adds 8 tokens to every session and 343 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.
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.