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/adelie-squad/solosquad/prioritizationnpx skills add Adelie-Squad/solosquad --skill prioritizationgit clone --depth 1 https://github.com/Adelie-Squad/solosquadWrote 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/adelie-squad/solosquad/prioritization)<a href="https://agentmods.dev/skills/adelie-squad/solosquad/prioritization"><img src="https://agentmods.dev/badge/skills/adelie-squad/solosquad/prioritization.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.1 | $0.00050 | $0.00883 |
| Opus 5 | $0.00025 | $0.00441 |
| Sonnet 5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
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 6d 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
Prioritization Skill
9 Framework 매트릭스
| Framework | 형식 | 적용 컨텍스트 |
|---|---|---|
| RICE | (Reach × Impact × Confidence) / Effort | 분기 로드맵, 기능 우선순위 |
| ICE | (Impact + Confidence + Ease) / 3 | 빠른 직관 비교, ≤10 후보 |
| Kano | Must-have / Performance / Excitement / Indifferent / Reverse | 신규 기능 분류 |
| Opportunity Score | Importance × (1 - Satisfaction) | Discovery 단계, unmet need |
| MoSCoW | Must / Should / Could / Won't | Release 단위 분류 |
| Weighted | Σ (weight × score) | 다기준 의사결정 (technical + business) |
| Eisenhower | Urgent × Important 2×2 | Solo founder 일정 |
| Value vs Effort | 2×2 matrix | quick wins 식별 |
| Cost of Delay | $$ / week | 의존성 / 시간민감 작업 |
Framework 선택 가이드 (post-labeling)
PM 이 후보 framework 를 직접 처방하지 않고, 컨텍스트에서 어떤 분류가 자연스러운지 식별:
- 후보가 N≥20 → RICE
- 후보가 N≤10 + 빠른 비교 → ICE
- discovery 단계, unmet need 발굴 → Opportunity Score
- release scope 결정 → MoSCoW
- 신규 vs 기존 mix → Kano
- 시간 민감 / 의존성 → Cost of Delay
계산 예시 (RICE)
candidates:
- title: "feature A"
reach: 1000 # 분기 영향 사용자 수
impact: 2 # 0.25 / 0.5 / 1 / 2 / 3 scale
confidence: 0.7 # 0-1
effort: 2 # person-month
rice_score: 700 # (1000 * 2 * 0.7) / 2
- title: "feature B"
reach: 500
impact: 3
confidence: 0.5
effort: 1
rice_score: 750
출력
{
"framework_used": "RICE",
"framework_rationale": "후보 23개 → RICE 적합",
"ranked": [
{ "id": "feature-B", "score": 750, "rank": 1 },
{ "id": "feature-A", "score": 700, "rank": 2 }
],
"recommended": ["feature-B"],
"deferred": ["feature-X"]
}
Anti-Sycophancy
- ❌ "feature B 가 더 좋아 보입니다"
- ✅ "feature B 가 RICE 750 으로 1위. effort < 2 인 조건에서. effort 가 1.5 이상으로 재추정되면 feature A 가 1위로 역전."
Reference
- phuryn/pm-skills/pm-execution/prioritization-frameworks (9 framework)
- Intercom RICE framework
- Kano model
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.
- 6d ago First seen · 96 lines · 50 tokens per session scan A 307329795e63
prioritization is a skill published in the GitHub repository Adelie-Squad/solosquad (19 stars, last pushed 15d ago), licensed MIT. It adds 50 tokens to every session and 883 once invoked, about $0.0003 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
saas-launcher
Sıfırdan production-ready bir SaaS uygulaması kur. Ödeme, kimlik doğrulama, veritabanı, e-posta, landing page, SEO ve API güvenliği dahil tüm katmanları kapsar. Kullanıcı SaaS kurmak, web uygulaması başlatmak, AI aracı oluşturmak veya online ürün çıkarmak istediğinde bu skill'i kullan — "startup kur", "proje başlat"…
saas-api-security
SaaS uygulaması için API güvenlik katmanı kur. Rate limiting, plan bazlı erişim kontrolü, input validation, hata yönetimi, CORS ve health check. Bu skill'i kullanıcı API güvenliği, rate limiting, yetkilendirme, input doğrulama, hata yönetimi veya API koruması ile ilgili bir şey istediğinde kullan. "API'yi koru", "rate…
saas-payments
SaaS uygulaması için ödeme ve abonelik sistemi kur. Stripe veya Lemon Squeezy ile checkout, webhook, abonelik yönetimi, fiyatlandırma planları ve müşteri portalı yapılandır. Bu skill'i kullanıcı ödeme, abonelik, fiyatlandırma, Stripe, gelir, plan, subscription veya checkout ile ilgili bir şey istediğinde kullan. "Para…
saas-analytics
SaaS uygulaması için PostHog analytics ve ürün analizi kur. Event tracking, kullanıcı tanımlama, feature flag, session replay, funnel analizi ve gizlilik uyumlu yapılandırma. Bu skill'i kullanıcı analytics, PostHog, event tracking, kullanıcı davranışı, feature flag, A/B test, dönüşüm analizi veya metrik takibi ile…
saas-testing
SaaS uygulaması için test stratejisi kur. Vitest ile birim test, Playwright ile E2E test, API route testi, webhook mock, Stripe test modu ve CI entegrasyonu. Bu skill'i kullanıcı test, test yazma, E2E, birim test, Playwright, Vitest, coverage veya kalite güvencesi ile ilgili bir şey istediğinde kullan. "Test yaz"…
saas-deployment
SaaS uygulamasını production'a taşı. Vercel, Railway veya Fly.io ile deployment, domain yapılandırması, SSL, ortam değişkenleri, CI/CD, izleme ve operasyonel hazırlık. Bu skill'i kullanıcı deploy, yayınlama, production, hosting, domain, SSL, CI/CD, monitoring veya "siteyi canlıya al" ile ilgili bir şey istediğinde…