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/nicepkg/ai-workflow/prioritization-effort-impactnpx skills add nicepkg/ai-workflow --skill prioritization-effort-impactgit clone --depth 1 https://github.com/nicepkg/ai-workflowWrote 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/nicepkg/ai-workflow/prioritization-effort-impact)<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/prioritization-effort-impact"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/prioritization-effort-impact.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 | $0.00096 | $0.03071 |
| Opus 5 | $0.00048 | $0.01536 |
| Sonnet 5 | $0.00019 | $0.00614 |
| Haiku 4.5 | $0.00010 | $0.00307 |
Grade A, and why
prioritization-effort-impact 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 yesterday.
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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritization: Effort-Impact Matrix
Table of Contents
- Purpose
- When to Use
- What Is It?
- Workflow
- Common Patterns
- Scoring Frameworks
- Guardrails
- Quick Reference
Purpose
Transform overwhelming backlogs and option lists into clear, actionable priorities by mapping items on a 2x2 matrix of effort (cost/complexity) vs impact (value/benefit). Identify quick wins (high impact, low effort) and distinguish them from big bets (high impact, high effort), time sinks (low impact, high effort), and fill-ins (low impact, low effort).
When to Use
Use this skill when:
- Backlog overflow: You have 20+ items (features, bugs, tasks, ideas) and need to decide execution order
- Resource constraints: Limited time, budget, or people force trade-off decisions
- Strategic planning: Choosing between initiatives, projects, or investments for quarterly/annual roadmaps
- Quick wins needed: Stakeholders want visible progress fast; you need high-impact low-effort items
- Trade-off clarity: Team debates "should we do A or B?" without explicit effort/impact comparison
- Alignment gaps: Different stakeholders (eng, product, sales, exec) have conflicting priorities
- Context switching: Too many simultaneous projects; need to focus on what matters most
- New PM/leader: Taking over a backlog and need systematic prioritization approach
Common triggers:
- "We have 50 feature requests, where do we start?"
- "What are the quick wins?"
- "Should we do the migration or the new feature first?"
- "How do we prioritize technical debt vs new features?"
- "What gives us the most bang for our buck?"
What Is It?
Effort-Impact Matrix (also called Impact-Effort Matrix, Quick Wins Matrix, or 2x2 Prioritization) plots each item on two dimensions:
- X-axis: Effort (time, cost, complexity, risk, dependencies)
- Y-axis: Impact (value, revenue, user benefit, strategic alignment, risk reduction)
What ships with it
3 files 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.
- yesterday First seen · 226 lines · 96 tokens per session scan A 3cada32528c8
prioritization-effort-impact is a skill published in the GitHub repository nicepkg/ai-workflow (283 stars, last pushed 7mo ago), licensed MIT. It adds 96 tokens to every session and 3,071 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-09-03.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…
triage
Triage open herdr GitHub issues into a concise decision-first Markdown table. Use when the user says "triage", asks to triage open issues, asks which issues need attention, or wants issue priority/recommendation lights for herdr.
backlog-technical-project-manager
Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.