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.
npx agentmods add skills/wirasm/prp/prp-worklistnpx skills add Wirasm/prp --skill prp-worklistgit 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.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.00540 |
| Opus 5 | $0.00020 | $0.00270 |
| Sonnet 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 3d 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.
- 3d 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,240 stars, last pushed 6d ago), licensed MIT. It adds 41 tokens to every session and 540 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…