PRP is a collection of prompts and workflows for AI-assisted software development with Claude Code. Its Product Requirement Prompts combine product requirements, selected codebase context, and an execution runbook so a coding agent can implement a vertical slice of software. The catalogue entries are the project’s own skills, agents, instructions, hook, and plugin workflows.
Borrowing it
Nothing to install: this file belongs to Wirasm/prp. 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/prp/development/.agents/skills/prp-pr/SKILL.mdgit clone --depth 1 https://github.com/Wirasm/prpWrote 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/skills/wirasm/prp/prp-pr)<a href="https://agentmods.dev/skills/wirasm/prp/prp-pr"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-pr/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/skills/wirasm/prp/prp-pr"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01194 |
| Opus 5.5 | $0.00022 | $0.00478 |
| Sonnet 5.5 | $0.00011 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
prp-pr 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments:
$ARGUMENTS(and$1,$2, ...) refer to the arguments given when this skill was invoked. Take them from the user's request; if absent, infer them from the conversation.
Create Pull Request
Create a clear, reviewer-friendly GitHub pull request for the completed work on the current branch.
Arguments: $ARGUMENTS
Scope
Run this at the PR-creation step after the requested work has been done by the current agent, a subagent, or another collaborator. Ensure every change belonging to that work is committed before opening the PR. If intended changes remain uncommitted, invoke $prp-commit with a natural-language target that identifies only those changes, then verify the resulting commit. Never sweep unrelated worktree changes into the commit.
The pull request itself is the artifact; do not create a separate local PR document.
1. Establish the PR target
Inspect the current branch, repository instructions, remote branches, and Git history. Determine the base in this order:
- An explicit
--base <branch>. - The base recorded on an existing PR for this branch.
- The repository's documented development flow.
- Branch ancestry against likely integration branches such as
development,dev, and the remote default branch. - The remote default branch as a fallback.
Use the same resolved base for every log, diff, and PR command. Never assume main. If the evidence is genuinely ambiguous, stop and ask rather than opening the PR against a guessed target.
Check whether any open or closed PR already exists for the current branch. If one exists, return its URL and state instead of creating a duplicate.
2. Validate the committed work
- Re-read
git statusand the diff after any commit to confirm no intended changes were omitted. - Confirm the current branch is not the resolved base and contains commits ahead of it.
- Fetch current remote state, then read the complete merge-base diff and commit range against the resolved base—not only the file list or diff stat.
- Compare the diff with the user's requested outcome and repository instructions. Stop if the branch does not contain the intended work or includes unexplained scope.
- Find the repository's pull request template in its supported root,
.github, ordocslocations. If several templates could apply and the correct one cannot be inferred, ask which to use.
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 · 102 lines · 56 tokens per session scan A 8165ed94f6f0
prp-pr is a skill published in the GitHub repository Wirasm/prp (2,264 stars, last pushed 18d ago), licensed MIT. It adds 56 tokens to every session and 1,194 once invoked, about $0.0002 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.