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 skills/mort-lab/excel-mcp/prp-core-runnernpx skills add mort-lab/excel-mcp --skill prp-core-runnergit 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/skills/mort-lab/excel-mcp/prp-core-runner)<a href="https://agentmods.dev/skills/mort-lab/excel-mcp/prp-core-runner"><img src="https://agentmods.dev/badge/skills/mort-lab/excel-mcp/prp-core-runner.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.00057 | $0.00639 |
| Opus 5 | $0.00028 | $0.00319 |
| Sonnet 5 | $0.00011 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
prp-core-runner 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 6d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRP Core Workflow Runner
Instructions
When the user requests to implement a feature using the PRP workflow or wants end-to-end automation from idea to PR, use the SlashCommand tool to invoke /prp-core-run-all with the user's feature description as the argument.
Step-by-step execution:
- Invoke the workflow: Use SlashCommand tool with
/prp-core-run-all {feature-description} - Monitor progress: The workflow will execute 5 steps in sequence:
- Create a conventional git branch
- Generate comprehensive PRP document
- Execute the PRP implementation
- Create atomic git commit
- Create pull request
- Handle failures: If any step fails:
- Report which step failed and why
- Do NOT proceed to subsequent steps
- Provide actionable guidance for fixing the issue
- Report completion: When all steps succeed, confirm the workflow completed and provide the PR URL
Error Handling:
- Stop execution immediately if any validation fails
- Report the specific error clearly
- Guide the user on how to resolve the issue
- Do not attempt to auto-fix complex validation failures
Examples
Example 1: Autonomous invocation
User: "Can you implement user authentication using JWT with the PRP workflow?"
Assistant: I'll use the prp-core-runner skill to execute the complete PRP workflow for implementing JWT authentication.
[Invokes: /prp-core-run-all Implement user authentication using JWT]
Example 2: Feature request
User: "I need to add a search API with Elasticsearch integration using PRP"
Assistant: I'll run the full PRP workflow to implement the search API with Elasticsearch.
[Invokes: /prp-core-run-all Add search API with Elasticsearch integration]
Example 3: Refactoring with PRP
User: "Use the PRP methodology to refactor the database layer for better performance"
Assistant: I'll execute the PRP workflow for refactoring the database layer.
[Invokes: /prp-core-run-all Refactor database layer for better performance]
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.
- 6d ago First seen · 75 lines · 57 tokens per session scan A 311ed2d24626
prp-core-runner is a skill published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 28d ago), licensed MIT. It adds 57 tokens to every session and 639 once invoked, about $0.0003 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
planning-and-task-breakdown
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.