execute-prp

A command that implements a Product Requirement Prompt file, which is a detailed specification for building a feature or product. It takes the file path supplied by the user as its input.

In plain words
What is it for?
Use it to read a PRP and its referenced files, understand the requirements, and build the specified change.
Why use it?
It turns a prepared requirements document into an implementation task without requiring the instructions to be copied into the conversation.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/wirasm/dylan/execute-prp
Clone the repo
git clone --depth 1 https://github.com/Wirasm/dylan

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 60 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00060
Opus 5 $0.00000 $0.00030
Sonnet 5 $0.00000 $0.00012
Haiku 4.5 $0.00000 $0.00006

Measured yesterday against content hash 5b49ec6e564e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.claude/commands/execute-prp.md · 10 lines

What it actually says

Implement a new PRP

Please take the following PRP file $ARGUMENTS and implement it.

Ingest all of the information in the PRP file and any reference doucments or files to understand the requirements

Think hard before you start implementing the PRP

Execute when ready

Changes

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.

  1. yesterday First seen · 10 lines · 0 tokens per session scan A 5b49ec6e564e

Subscribe to this mod's changes

execute-prp is a command published in the GitHub repository Wirasm/dylan (37 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 60 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.