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 stefanoskarakasis/Product-Marketing-Skills --skill prioritization-frameworksgit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-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/stefanoskarakasis/product-marketing-skills/prioritization-frameworks)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/prioritization-frameworks"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/prioritization-frameworks/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/stefanoskarakasis/product-marketing-skills/prioritization-frameworks"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/prioritization-frameworks.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.00092 | $0.03570 |
| Opus 5 | $0.00046 | $0.01785 |
| Sonnet 5 | $0.00018 | $0.00714 |
| Haiku 4.5 | $0.00009 | $0.00357 |
Grade A, and why
prioritization-frameworks 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 today.
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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritization-Frameworks — Skill
How This Works
Prioritization frameworks are decision tools, not prescriptions. Your job is to pick the right one for the question, apply it with integrity, and translate the output into a tier recommendation (T1–T4) that drives GTM resource allocation.
The skill runs in 7 core steps:
Step 0 — Load brain context (ICP, positioning, revenue levers) and guardrails from /context/meta-patterns.md, if it exists (e.g., "frameworks without customer confidence >7 have led to prior T1 overstatements" — an example pattern shape, not a claim already observed).
Step 1 — Intake: Understand what you're deciding (launch tier? roadmap backlog? strategic choice?) and what signals you have.
Step 2 — Framework selection: Based on decision type and available data, recommend the right framework(s).
Step 3 — Scoring: Run the framework, surface Confidence weaknesses, apply Quality Gates.
Step 4 — Tier translation: Convert framework output to T1–T4 with one-sentence rationale.
Step 5 — Audit & recommendation: Pressure-test the tier assignment; deliver go/no-go on tier or recommend additional validation.
Step 6 — Output: Tier assignment card + scoring table + next step.
Step 7 — Learning Close: log the session to /context/skill-sessions.md.
Trigger
- When: Choosing and applying a prioritization framework to score initiatives, backlog items, or strategic choices, and translating the result into a launch tier (T1–T4).
- Not for: Assigning a launch tier directly from a GTM brief without a scoring pass → use
go-to-market-strategy. Messaging hierarchy specifically → run Kano here, then hand off topositioning-messaging. - Example prompts:
- "Help me prioritize this backlog"
- "What framework should I use to decide between these two initiatives?"
- "Score this with RICE"
- "Which of these should we do first?"
Inputs
- Args: What's being decided (launch tier, backlog, strategic choice), number of initiatives being compared, available signals, timeline, audience for the output. Free format — Step 1 intake fills gaps conversationally.
- Defaults: If brain context is unavailable, this skill still runs — brain sharpens how "Opportunity" and "Impact" are interpreted, but is not a hard blocker.
- Context keys:
/foundation/brain.md— optional but recommended. Sections 2 (ICP), 3 (Positioning), 5 (Revenue Levers)./context/meta-patterns.md— optional; recurring patterns the user has logged from prior scoring sessions.- Brain contract: Reads Sections 2, 3, 5. Writes: none — this skill does not write to
/foundation/brain.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +2 lines aa7ef91bfb98
- 12d ago First seen · 342 lines · 92 tokens per session scan A e829270d5d54
prioritization-frameworks is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (5 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 3,570 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-31.
Other skills, from other repositories
becoming-senior-pm
Use this skill when the user asks "how do I become a senior PM", "what does senior PM actually mean", "I want to get promoted to senior", "what's the difference between PM and senior PM", "I've been a PM for 2–3 years and want to grow", "my manager says I need to work more strategically", "I'm stuck at PM level", or…
founding-pm
Use this skill when the user says "I'm the first PM", "founding PM", "I joined a startup as the only PM", "how do I set up PM processes from scratch", "no PM infrastructure exists", "I'm building the PM function", "what should a first PM do in 90 days", or is navigating the unique challenges of being an early-stage PM…
memory
Use this skill when the user asks to "update my PM Copilot memory", "save this to my profile", "remember that", "update my context", "update my product context", "save this decision", "add this to my memory", "track this risk", "mark this risk as resolved", "add a lesson learned", "save these stakeholder notes", or…
onboarding
Use this skill when the user says "set up PM Copilot", "run onboarding", "I'm new here", "help me get started", "initialize my profile", "set up my context", "configure PM Copilot", or when memory/user-profile.md exists but has no content filled in (all fields are still placeholder comments). Also use this skill when…
prd-authoring
Use this skill when the user asks to "write a PRD", "write a spec", "product requirements document", "generate a PRD", "turn this into a spec", "create product requirements", "write acceptance criteria", or explicitly asks for a PRD or product specification. This skill writes a full PRD. For a chained workflow with…
technical-pm
Use this skill when the user asks about "working with engineers as a PM", "how technical should a PM be", "I feel out of my depth with engineers", "how to earn engineering trust", "how to read code as a PM", "should I learn to code", "bridging the gap with engineering", "technical credibility for PMs", or wants to…