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.
git 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/generate-prp)<a href="https://agentmods.dev/commands/croffasia/cc-blueprint-toolkit/generate-prp"><img src="https://agentmods.dev/badge/commands/croffasia/cc-blueprint-toolkit/generate-prp/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/commands/croffasia/cc-blueprint-toolkit/generate-prp"><img src="https://agentmods.dev/badge/commands/croffasia/cc-blueprint-toolkit/generate-prp.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.00015 | $0.01443 |
| Opus 5.5 | $0.00006 | $0.00577 |
| Sonnet 5.5 | $0.00003 | $0.00289 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
generate-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 1mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PRP
Feature file: $ARGUMENTS
Generate PRP (Product Requirements & Plans) through validated research and codebase analysis.
Workflow Summary
Two-phase approach: validate completeness (Phase 1), then research (Phase 2).
CRITICAL: PRP must contain ALL context - research findings, documentation URLs, code examples. The executor agent sees only the final PRP document, not your research process.
Research Process
Phase 1: Initial Discovery & Task Validation (Validate task completeness before deep research)
-
Preflight Analysis (Use subagent:
bp:preflight-prp)- Quick scan of project structure for similar features/patterns
- Analyze user's task description for business logic completeness
- Identify gaps in user requirements and missing business logic details:
- User flows and interaction patterns
- Data requirements and relationships
- Integration points with existing features
- Edge cases and error scenarios
- UI/UX expectations and constraints
- Language Guidelines for Questions:
- Ask clarification questions in the same language the user wrote the initial task
- Wait for user responses and analyze thoroughly
- Generate targeted clarification questions if gaps identified
- Make proceed/clarify recommendation with clear reasoning
-
Decision Gate:
- IF bp:preflight-prp recommends PROCEED → Continue to Phase 2
- IF bp:preflight-prp identifies gaps → Stop and ask clarifying questions
- ONLY continue to comprehensive research after user provides missing details
- Use surface discovery findings to inform Phase 2 research focus
Phase 2: Comprehensive Research Phase (After task validation - Codebase first, then smart external research)
- Codebase Analysis (Use subagent:
bp:codebase-research)- Search for similar features/patterns in the codebase
- Identify files to reference in PRP
- Note existing conventions to follow
- Check test patterns for validation approach
- CRITICAL: Document what components/libraries/patterns already exist
- ASSESS: Determine knowledge gaps that truly need external research
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.
- 1mo ago First seen · 159 lines · 15 tokens per session scan A b9d3d766bf24
generate-prp is a command published in the GitHub repository croffasia/cc-blueprint-toolkit (195 stars, last pushed 11mo ago), licensed MIT. It adds 15 tokens to every session and 1,443 once invoked, about $0.0001 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-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.