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.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00873 |
| Sonnet 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 8d 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.
- 8d ago First seen · 176 lines · 92 tokens per session scan A d4a08603ba28
prioritize is a skill published in the GitHub repository mshadmanrahman/pm-pilot (20 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 1,747 once invoked, about $0.0005 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
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.