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 skills add Uxcel-Lab/product-skills --skill prioritizationgit clone --depth 1 https://github.com/Uxcel-Lab/product-skillsWrote 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/uxcel-lab/product-skills/prioritization)<a href="https://agentmods.dev/skills/uxcel-lab/product-skills/prioritization"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/prioritization/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/uxcel-lab/product-skills/prioritization"><img src="https://agentmods.dev/badge/skills/uxcel-lab/product-skills/prioritization.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.00159 | $0.02946 |
| Opus 5 | $0.00079 | $0.01473 |
| Sonnet 5 | $0.00032 | $0.00589 |
| Haiku 4.5 | $0.00016 | $0.00295 |
Grade A, and why
pm-prioritization 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 9d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritization Skill
How this skill behaves (read first)
This is a generative skill, and prioritization is where good intentions turn into a feature factory. Claude's defaults are the failure modes: reach for RICE for everything (the wrong tool for a brand-new product, where reach scores near zero), produce scores that look objective but rest on guesses, rank without tracing to strategy (so the loudest stakeholder wins), treat the backlog as a dump, and pretend you can optimize time, scope, and quality at once. Strong prioritization is the opposite: criteria derived from strategy, the right framework for the situation, scoring used to surface trade-offs rather than fake precision, sequencing that protects flow, and a defensible "no." So this skill gates:
- Establish the strategy, the stage/constraints, and the decision's reversibility — these determine the criteria, the framework, and how much rigor is warranted.
- Apply the always-true core — derive criteria from strategy, treat the backlog as a funnel, score to expose trade-offs, balance value × business × feasibility, make trade-offs explicit, sequence don't just rank, say no with context.
- Surface the context-dependent decisions (which framework, scoring rigor, roadmap horizon, appetite vs. estimate, bets vs. tactical) with trade-offs.
Then it hands off to pm-prioritization-rigor-audit (its primary pairing), plus pm-okr-metric-validity-audit, pm-assumption-rigor-audit, and — for high-stakes irreversible calls — pm-decision-quality-audit.
Scope: this skill owns the prioritization decision and its sequencing. It defers the roadmap artifact and its communication to pm-roadmap, the strategy itself to pm-vision-strategy, finding/validating the problems to pm-discovery and pm-problem-statement, and the spec to pm-product-spec.
Step 0 — Establish context before prioritizing
Ask if not known; state the assumption if proceeding without an answer:
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.
- 9d ago First seen · 104 lines · 159 tokens per session scan A 75e20a492fa4
pm-prioritization is a skill published in the GitHub repository Uxcel-Lab/product-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 159 tokens to every session and 2,946 once invoked, about $0.0008 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-31.
Other skills, from other repositories
pm-brainstorm
A guided brainstorming workflow for exploring a new product idea before detailed research or requirements work. It collects basic information about the product, users, and problem through staged questions.
pm-priority
A Chinese-language procedure for ranking several product requests when time or resources are limited. It supports scoring or grouping methods such as RICE, KANO, and MoSCoW to decide what should be done first.
start-super-pm
Use when starting any product management task - automatically detects task type and invokes appropriate PM skill using intelligent routing.
pm-change
A requirements-change workflow for recording a proposed change, assessing its effects, and deciding whether to approve it.
pm-risk
A structured process for identifying, rating, responding to, and monitoring project risks before important delivery points or launch.
pm-user-story
A workflow for turning product requirements into user stories: short statements of what a user wants and why, with acceptance criteria for checking the result.