Borrowing it
Nothing to install: this file belongs to Wirasm/dylan. 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/Wirasm/dylan/develop/.claude/commands/create-prp.mdgit clone --depth 1 https://github.com/Wirasm/dylanWrote 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/wirasm/dylan/create-prp)<a href="https://agentmods.dev/commands/wirasm/dylan/create-prp"><img src="https://agentmods.dev/badge/commands/wirasm/dylan/create-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/wirasm/dylan/create-prp"><img src="https://agentmods.dev/badge/commands/wirasm/dylan/create-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.00000 | $0.00572 |
| Opus 5.5 | $0.00000 | $0.00229 |
| Sonnet 5.5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
create-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 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YOU MUST READ THESE FILES AND FOLLOW THE INSTRUCTIONS IN THEM. Start by reading the concept_library/cc_PRP_flow/README.md to understand what a PRP Then read concept_library/cc_PRP_flow/PRPs/base_template_v1 to understand the structure of a PRP.
Think hard about the concept
Help the user create a comprehensive Product Requirement Prompt (PRP) for: $ARGUMENTS
Instructions for PRP Creation
Research and develop a complete PRP based on the feature/product description above. Follow these guidelines:
Research Process
Begin with thorough research to gather all necessary context:
-
Documentation Review
- Check for relevant documentation in the
ai_docs/directory - Identify any documentation gaps that need to be addressed
- Ask the user if additional documentation should be referenced
- Check for relevant documentation in the
-
WEB RESEARCH
- Use web search to gather additional context
- Research the concept of the feature/product
- Look into library documentation
- Look into example implementations on StackOverflow
- Look into example implementations on GitHub
- etc...
- Ask the user if additional web search should be referenced
-
Template Analysis
- Use
concept_library/cc_PRP_flow/PRPs/base_template_v1as the structural reference - Ensure understanding of the template requirements before proceeding
- Review past templates in the PRPs/ directory for inspiration if there are any
- Use
-
Codebase Exploration
- Identify relevant files and directories that provide implementation context
- Ask the user about specific areas of the codebase to focus on
- Look for patterns that should be followed in the implementation
-
Implementation Requirements
- Confirm implementation details with the user
- Ask about specific patterns or existing features to mirror
- Inquire about external dependencies or libraries to consider
PRP Development
Create a PRP following the template in concept_library/cc_PRP_flow/PRPs/base_template_v1, ensuring it includes the same structure as the template.
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 · 77 lines · 0 tokens per session scan A 069ce58b41ce
create-prp is a command published in the GitHub repository Wirasm/dylan (38 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 572 tokens. 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 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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.