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-worklist/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-worklist)<a href="https://agentmods.dev/skills/wirasm/prp/prp-worklist"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-worklist/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-worklist"><img src="https://agentmods.dev/badge/skills/wirasm/prp/prp-worklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 42 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00041 | $0.00540 |
| Opus 5.5 | $0.00016 | $0.00216 |
| Sonnet 5.5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
prp-worklist 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.
What it actually says
PRP Worklist
Incubating. Deliberately underspecified. Make your own judgements, then say what you chose and why — the good choices get recorded and prescribed later. Do not wait for a spec that does not exist yet.
Render the open issues and PRs of a repository as an artifact the maintainer can look at, and offer it. Not a list of everything — a view of what to take next.
The job
A tracker sorts by number and shouts every label equally loudly. That is the tool's view, not the maintainer's. Produce the maintainer's view.
Read the tracker with gh. Then decide what is worth showing and how to show it.
What this maintainer cares about
Considerations, not fields to emit. Weigh them, drop the ones that do not apply, add what the repository makes obvious:
- Blocked on a decision, or takeable now. The distinction he asks for most.
- Stale. An issue whose premise has moved — the code it describes was deleted, the blocker it waits on closed. Staleness should be visible, not discovered on starting the work.
- Near-duplicates. Two issues that are one thing. Cheap to spot in a list, expensive to find after both are filed.
- His, or someone else's. Different obligations as a maintainer.
- Blast radius rather than severity. What breaks, and for whom, if this is left.
Shape
Yours to decide. Markdown or HTML, grouped or ranked, dense or spacious — whatever makes the answer to "what do I take next" obvious in a glance.
Then offer it rather than pasting it: write the file to this project's ~/.prp/<key>/ store
and print a link the operator can open. If a helm-canvas skill is available, follow it.
Report your choices
End with a short note: what you grouped by, what you left out, what you could not tell from the tracker alone. That note is the point of this skill being loose — it is how the shape gets decided by evidence rather than up front.
If something here got in your way, say that too.
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 · 52 lines · 41 tokens per session scan A 79bbae1ec718
prp-worklist is a skill published in the GitHub repository Wirasm/prp (2,264 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 540 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…