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/pietrodelfranco/mcpserver/prp-mcp-executegit clone --depth 1 https://github.com/pietrodelfranco/mcpserverWrote 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/pietrodelfranco/mcpserver/prp-mcp-execute)<a href="https://agentmods.dev/commands/pietrodelfranco/mcpserver/prp-mcp-execute"><img src="https://agentmods.dev/badge/commands/pietrodelfranco/mcpserver/prp-mcp-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.1 | $0.00053 | $0.00366 |
| Opus 5 | $0.00026 | $0.00183 |
| Sonnet 5 | $0.00011 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
prp-mcp-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 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.
This is a copy
100% identical to prp-mcp-execute — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Execute MCP Server PRP
Execute a comprehensive Product Requirement Prompt (PRP) for building Model Context Protocol (MCP) servers with authentication, database integration, and Cloudflare Workers deployment.
PRP to execute: $ARGUMENTS
Purpose
Execute MCP server PRPs with comprehensive validation, testing, and deployment verification following the proven patterns from this codebase.
Execution Process
-
Load & Analyze PRP
- Read the specified PRP file completely
- Understand all context, requirements, and validation criteria
- Create comprehensive todo list using TodoWrite tool
- Identify all dependencies and integration points
-
Context Gathering & Research
- Use Task agents to research existing MCP server patterns
- Study authentication flows and database integration patterns
- Research Cloudflare Workers deployment and environment setup
- Gather all necessary documentation and code examples
-
Implementation Phase
- Execute all implementation tasks in the correct order
- Follow TypeScript patterns from the existing codebase
- Implement MCP tools, resources, and authentication flows
- Add comprehensive error handling and logging
Notes
- Uses TodoWrite tool for comprehensive task management
- Follows all patterns from the proven codebase implementation
- Includes comprehensive error handling and recovery
- Optimized for Claude Code's validation loops
- Production-ready with monitoring and logging
- Compatible with MCP Inspector and Claude Desktop
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 · 45 lines · 53 tokens per session scan A 7d3e3b03cd70
prp-mcp-execute is a command published in the GitHub repository pietrodelfranco/mcpserver (0 stars, last pushed 1y ago), licensed MIT. It adds 53 tokens to every session and 366 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to prp-mcp-execute, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.