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 tomzx/agents --skill prioritize-issuesgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/prioritize-issues)<a href="https://agentmods.dev/skills/tomzx/agents/prioritize-issues"><img src="https://agentmods.dev/badge/skills/tomzx/agents/prioritize-issues/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/tomzx/agents/prioritize-issues"><img src="https://agentmods.dev/badge/skills/tomzx/agents/prioritize-issues.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.00027 | $0.00752 |
| Opus 5 | $0.00014 | $0.00376 |
| Sonnet 5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
prioritize-issues 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prioritize Issues
Scores and ranks open GitHub issues using the RICE framework (Reach, Impact, Confidence, Effort) to produce a prioritized backlog ordered by highest value first.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, operate on
$REPO. ghCLI authenticated with read access to the target repository- Repository in
owner/repoformat ($1), or omit to infer from the current working directory
RICE Scoring
RICE score = (Reach × Impact × Confidence) / Effort
| Factor | Scale | Description |
|---|---|---|
| Reach | 1–10 | How many users are affected per period |
| Impact | 1–5 | Effect on the goal (1=minimal, 5=massive) |
| Confidence | 0.5–1.0 | How confident we are in the estimates |
| Effort | 0.5–5 | Person-weeks of work required |
Steps
- Fetch all open issues:
ghx issue list [--repo $1] --state open --limit 100 - For each issue, read its title, description, and labels.
- Estimate RICE factors based on:
urgentlabel → higher Reach/Impactimportantlabel → higher Impact- Scope described in the issue body → Effort
- Compute the RICE score for each issue.
- Sort issues by RICE score descending.
- Output the prioritized backlog table and scoring notes.
Output Format
## Prioritized Backlog
| Rank | Issue | Title | Reach | Impact | Confidence | Effort | RICE Score |
|---|---|---|---|---|---|---|---|
| 1 | #12 | Fix checkout crash | 8 | 5 | 0.9 | 1 | 36.0 |
| 2 | #7 | Add OAuth login | 6 | 4 | 0.8 | 3 | 6.4 |
## Scoring Notes
<Explain significant assumptions or confidence factors for any non-obvious scores.>
Example Usage
Scenario 1: Rank a full backlog
/prioritize-issues owner/myrepo
Fetches all open issues, scores them on RICE, and outputs a ranked table.
Scenario 2: Focus on a milestone
/prioritize-issues owner/myrepo
User says "only issues in milestone v2.0." Filter with:
ghx issue list [--repo $1] --milestone "v2.0" --state open
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 · 84 lines · 27 tokens per session scan A 26b9e3a0051c
prioritize-issues is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 752 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.