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.
curl -O https://raw.githubusercontent.com/mort-lab/excel-mcp/main/.claude/skills/prp-core-runner/SKILL.mdgit 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/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.
<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="Reviewed on agentmods" width="80" 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.5 | $0.00023 | $0.00256 |
| Sonnet 5.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 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.
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.
- 2mo 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 2mo ago), licensed MIT. It adds 57 tokens to every session and 639 once invoked, about $0.0002 per session on Opus 5.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
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.
git-workflow
Git best practices for version control and collaboration.
p4-stream-workflows
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. Use when: creating streams, branching, merging, copying between streams, integrating changes, switching workspaces, or managing stream specs in P4.
p4-workspace-setup
P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools. Use when: creating workspaces, configuring client specs, syncing files, switching workspaces, or checking workspace status in P4.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.