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 jerseycheese/agent-skills --skill prioritize-issuesgit clone --depth 1 https://github.com/jerseycheese/agent-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/jerseycheese/agent-skills/prioritize-issues)<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/prioritize-issues"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/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/jerseycheese/agent-skills/prioritize-issues"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/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.00117 | $0.01285 |
| Opus 5 | $0.00059 | $0.00642 |
| Sonnet 5 | $0.00023 | $0.00257 |
| Haiku 4.5 | $0.00012 | $0.00128 |
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 9d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Prioritization
1. Discover the repo
If the user didn't specify a repo, infer it:
gh repo view --json nameWithOwner -q .nameWithOwner
2. Fetch all open issues
Pull the full backlog — not just recent issues:
gh issue list --state open --limit 200 --json number,title,labels,createdAt,body,milestone,comments
If the repo has more than 200 open issues, paginate. Also fetch any recent comments on the top candidates to catch context updates:
gh issue view [NUMBER] --json number,title,body,labels,comments,createdAt,milestone
3. Pre-filter
Skip issues labeled wontfix, duplicate, invalid, or question. Skip closed issues (should be excluded by the list query, but double-check).
4. Score each issue
For each issue, assess these dimensions. You don't need to output the raw scores — use them internally to reason about rank.
Value (0-10)
| Factor | Points |
|---|---|
| User-facing bug that breaks functionality | +3 |
| User-facing improvement | +2 |
| Internal/no user impact | +0-1 |
| Unblocks multiple other issues | +2 |
| Unblocks one other issue | +1 |
| Aligned with active milestone or roadmap goal | +2-3 |
Labels: critical, blocking, P0 |
+2 |
Effort (0-10, lower is better)
| Factor | Points |
|---|---|
| Major architectural change | +4 |
| Touches many files/systems | +3 |
| Moderate complexity | +2 |
| Simple, well-scoped change | +1 |
| Requires extensive E2E + manual testing | +3 |
| Unit tests only | +1 |
| Breaking changes or migrations | +3 |
| Low-risk, isolated change | +0-1 |
Labels: good first issue, small, quick |
-1 (lower effort) |
Age bonus
Issues that have been open longer tend to get pushed down unfairly. Apply a small bonus:
- Open 2-8 weeks: +0.1
- Open 2-6 months: +0.3
- Open 6+ months: +0.5
This is a tiebreaker, not a primary driver. A low-value chore open for a year still loses to a critical bug opened yesterday.
Priority score
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.
- 9d ago First seen · 175 lines · 117 tokens per session scan A a7b67db8c147
prioritize-issues is a skill published in the GitHub repository jerseycheese/agent-skills (1 stars, last pushed 7d ago), licensed MIT. It adds 117 tokens to every session and 1,285 once invoked, about $0.0006 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
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
cross-campaign
Discover and reference other camps, projects, and files across camp boundaries. Use when the user mentions another camp or campaign by name, references work done "in another project/camp", or needs to find/copy/compare code across camps.
fest-execution
Execute active festival tasks. Use when finding the next task, marking tasks completed/blocked/reset, committing with festival traceability, advancing workflow steps, and validating sequence progress.
fest-planning
Plan and scaffold festivals. Use when creating festival/phase/sequence/task structure, enforcing naming rules, linking festivals to projects, and promoting lifecycle states.
camp-workitems
Find, filter, choose, create, or adopt camp work items with camp workitem, camp wi, or camp workitems. Use when a user wants current active work across intents, designs, explore notes, festivals, or tracked workflow directories; when agents need safe camp workitem --json output; or when creating/adopting tracked…
fest-methodology
Use when the user mentions festivals, the fest CLI, phases, sequences, or tasks, or when working inside a festivals/ directory. Provides the core Festival methodology model so Claude understands the planning system.