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/croffasia/cc-blueprint-toolkit/execute-prpgit clone --depth 1 https://github.com/croffasia/cc-blueprint-toolkitWrote 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/croffasia/cc-blueprint-toolkit/execute-prp)<a href="https://agentmods.dev/commands/croffasia/cc-blueprint-toolkit/execute-prp"><img src="https://agentmods.dev/badge/commands/croffasia/cc-blueprint-toolkit/execute-prp.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.00011 | $0.00447 |
| Opus 5 | $0.00005 | $0.00224 |
| Sonnet 5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
execute-prp 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 5d 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 BASE PRP
Implement a feature using the PRP file.
PRP File: $ARGUMENTS
Execution Process
-
Load PRP
- Read the specified PRP file
- Understand all context and requirements
- Follow all instructions in the PRP and extend the research if needed
- Ensure you have all needed context to implement the PRP fully
- Do more web searches and codebase exploration as needed
-
Plan Implementation
- Think hard before you execute the plan. Create a comprehensive plan addressing all requirements.
- Break down complex tasks into smaller, manageable steps using your todos tools.
- Use the TodoWrite tool to create and track your implementation plan.
- CRITICAL: Study reference files specified in PRP - understand their exact structure, patterns, and organization.
- ALWAYS: Mirror the reference implementation patterns exactly - same file organization, naming conventions, component structure, and code patterns.
-
Execute the plan
- BEFORE coding each component: Read the corresponding reference file to understand its exact structure
- FOR each task: Look at reference implementation first, then adapt the pattern for your feature
- Execute the PRP following reference patterns exactly
- Implement all the code using established patterns
-
Validate
- Run each validation command
- Fix any failures
- Re-run until all pass
-
Complete
- Ensure all checklist items done
- Run final validation suite
- Report completion status
- Read the PRP again to ensure you have implemented everything
-
Reference the PRP
- You can always reference the PRP again if needed
Note: If validation fails, use error patterns in PRP to fix and retry.
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.
- 5d ago First seen · 57 lines · 11 tokens per session scan A 8031a5438978
execute-prp is a command published in the GitHub repository croffasia/cc-blueprint-toolkit (194 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 447 once invoked, about $0.0001 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-30.
Other commands, from other repositories
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
graphstack
Graph-first, automatically orchestrated AI development workflow. One prompt starts the entire lifecycle — from blank repo to production.
git-release-workflow
This command has been deprecated and merged into /dev:release.
check-web-perf
Diagnostic command to check web performance toolkit setup and dependencies.
diagnose-runtime
Quickly diagnose runtime performance issues in web applications including freezes, hangs, memory leaks, and slow performance.