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 mshadmanrahman/pm-pilot --skill prioritizegit clone --depth 1 https://github.com/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/prioritize)<a href="https://agentmods.dev/skills/mshadmanrahman/pm-pilot/prioritize"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/prioritize/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/mshadmanrahman/pm-pilot/prioritize"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/pm-pilot/prioritize.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.00092 | $0.01747 |
| Opus 5.5 | $0.00037 | $0.00699 |
| Sonnet 5.5 | $0.00018 | $0.00349 |
| Haiku 4.5 | $0.00009 | $0.00175 |
Grade A, and why
prioritize 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritize: Feature Ranking and Scoring
Score and rank features, initiatives, or backlog items using established PM frameworks. Auto-detects the right framework and mode from context.
When to Activate
- User says "prioritize", "rank these", "what should we build next?"
- User asks for RICE, ICE, WSJF, or any scoring framework
- User needs to make scope cuts or trade-off decisions
- User has a list of features and needs to decide order
Modes
Auto-detect from user phrasing. If ambiguous, ask.
| Mode | When | Output |
|---|---|---|
| Stack rank | "What should we build next?" | Ordered list with reasoning |
| Scoring | "Score these 10 features" | Framework table with scores |
| Opportunity assessment | "Where's the biggest opportunity?" | Gap analysis, underserved areas |
| Trade-off analysis | "Should we do A or B?" | Side-by-side comparison |
| Scope cut | "We need to cut scope" | Keep/cut/defer recommendations |
Detection heuristics
- "rank", "order", "what first", "what next" → Stack rank
- "score", "RICE", "ICE", "rate these" → Scoring
- "opportunity", "gap", "underserved" → Opportunity assessment
- "A or B", "trade-off", "which one", "compare" → Trade-off analysis
- "cut scope", "too much", "reduce", "what can we drop" → Scope cut
Frameworks
RICE (default for scoring mode)
Best for: Large backlogs, cross-team prioritization, when you need a defensible number.
| Feature | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|
| {name} | {users/qtr} | {0.25-3} | {50-100%} | {person-months} | {R×I×C/E} |
- Reach: How many users affected per quarter
- Impact: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal
- Confidence: 100% = high certainty, 80% = medium, 50% = low
- Effort: Person-months of work
ICE (default for quick decisions)
Best for: Fast prioritization, smaller teams, when RICE feels heavy.
| Feature | Impact | Confidence | Ease | ICE Score |
|---|---|---|---|---|
| {name} | {1-10} | {1-10} | {1-10} | {I×C×E} |
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 · 176 lines · 92 tokens per session scan A d4a08603ba28
prioritize is a skill published in the GitHub repository mshadmanrahman/pm-pilot (22 stars, last pushed 23d ago), licensed MIT. It adds 92 tokens to every session and 1,747 once invoked, about $0.0004 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
ops-standup
Cross-repo morning briefing. Aggregation of recent commits, PRs, CI, blockers and priorities of the day. Trigger when the user wants a standup, an activity summary, or to know what happened.
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode that implements and commits each story one by one. Trigger when the user wants to process a backlog, execute multiple stories, or launch an autonomous mode.
notion
Search, read, create, and update Notion pages via the Notion MCP.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
create-stories
Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.
day-one-patch
Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.