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.
git clone --depth 1 https://github.com/CrashBytes/claude-role-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/commands/crashbytes/claude-role-skills/backlog-prioritize)<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/backlog-prioritize"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/backlog-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/commands/crashbytes/claude-role-skills/backlog-prioritize"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/backlog-prioritize.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.00016 | $0.00460 |
| Opus 5 | $0.00008 | $0.00230 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
backlog-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.
What it actually says
Backlog Prioritization
Prioritize backlog items using a structured framework.
Arguments
Framework or context: $ARGUMENTS
Workflow
-
Select framework
- If specified, use the requested framework
- Default to RICE (most data-driven)
- Available: RICE, MoSCoW, WSJF, Value vs Effort
-
Gather backlog items
- If a project management MCP server is connected, fetch the current backlog
- If not, ask the user to list their backlog items
-
Apply the framework
RICE:
- Reach: How many users affected per quarter?
- Impact: Minimal (0.25), Low (0.5), Medium (1), High (2), Massive (3)
- Confidence: Low (50%), Medium (80%), High (100%)
- Effort: Person-months
- Score = (Reach × Impact × Confidence) / Effort
MoSCoW:
- Must Have: Required for the release to be viable
- Should Have: Important but not critical
- Could Have: Nice to have
- Won't Have: Explicitly out of scope for now
WSJF (Weighted Shortest Job First):
- Business Value + Time Criticality + Risk Reduction / Job Size
- Use Fibonacci scale (1, 2, 3, 5, 8, 13) for each factor
Value vs Effort:
- Score value 1-10 and effort 1-10
- Quadrants: Quick Wins (high value, low effort) → Major Projects → Fill-ins → Avoid
-
Output
- Ranked list with scores
- Visualization of the ranking (table format)
- Top 5 recommendations with rationale
- Items that need more information before they can be scored
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 · 54 lines · 16 tokens per session scan A ae1781beed93
backlog-prioritize is a command published in the GitHub repository CrashBytes/claude-role-skills (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 460 once invoked, about $0.0001 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 commands, from other repositories
contribute-to
Join an EXISTING, in-progress work item (issue or PR) as a contributor — walk the contribution loop toward a human-stated goal and success criteria, without the full spec chain.
create-ticket
Create a work-item ticket (GitHub issue / Jira) from an existing requirements.md, then promote its draft spec folder to docs/specs/ /.
finish-tasks
Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.
work-status
Report the current status of a work item by reading its spec files (requirements/design/tasks) and execution log. Read-only.
ledger-check
Audit all ledger files for drift (report; fix only on request).
triage
Promote ideas from Ideas.md into Epics or User Stories in the Epic backlog (dedup, typed ID, voice).