Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/richfrem/agent-plugins-skillsnpx agentmods add skills/richfrem/agent-plugins-skills/github-issue-prioritizerWrote 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/richfrem/agent-plugins-skills/github-issue-prioritizer)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/github-issue-prioritizer"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-prioritizer/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/richfrem/agent-plugins-skills/github-issue-prioritizer"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/github-issue-prioritizer.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.00073 | $0.00653 |
| Opus 5.5 | $0.00029 | $0.00261 |
| Sonnet 5.5 | $0.00015 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
github-issue-prioritizer 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 17d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Prioritizer (github-issue-prioritizer)
Computes deterministic priority ranks (P0-P3) for GitHub issues from friction tiers, recurrence frequency, and blockages.
Contents
Critical Constraints
- Scope Boundary: USE ONLY for calculating priority ranks (P0-P3) and syncing priority labels/fields. DO NOT USE for logging issues (use
github-issue-agent). - Deterministic Formula: Calculate priority ranks strictly using the weighted matrix in
priority-matrix.mdwithout manual override inflation. - Dry-Run Default: Preview calculated scores and proposed label diffs before mutating GitHub metadata.
- Rate-Limit Hygiene: Batch queries when prioritizing bulk backlogs to avoid secondary GitHub API limits.
Quick start
# Calculate priority score and preview update (dry-run)
python3 plugins/dev-utils/skills/github-issue-prioritizer/scripts/gh_issue_prioritize.py --issue 42
# Execute live priority label and Projects v2 update
python3 plugins/dev-utils/skills/github-issue-prioritizer/scripts/gh_issue_prioritize.py --issue 42 --execute
Workflow
- Phase 1: Issue Inspection: Retrieve issue metadata, friction tier labels (
tier:*), and linked blocker relationships. - Phase 2: Score Calculation: Evaluate score via matrix formula considering tier severity, recurrence count, and pipeline blocks.
- Phase 3: Payload Preview: Review proposed priority designation (
priority:P0throughpriority:P3) in preview mode. - Phase 4: Label & Field Sync: Apply the resulting priority label and update GitHub Projects v2 fields using
--execute.
Verification
# Audit skill compliance
python3 plugins/agent-scaffolders/scripts/audit_skill.py plugins/dev-utils/skills/github-issue-prioritizer --mode source
References
- priority-matrix.md - Ranking logic, weighting formula, and Python API.
- acceptance-criteria.md - Verification contracts and test criteria.
- fallback-tree.md - Missing label defaults and GraphQL fallback procedures.
What ships with it
6 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.
- 17d ago Changed · +21 lines 7f2565890892
- 1mo ago Changed · -13 lines · +30 tokens per session 3d753fad1916
- 1mo ago First seen · 55 lines · 43 tokens per session scan A b45bfa227000
github-issue-prioritizer is a skill published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 653 once invoked, about $0.0003 per session on Opus 5.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
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
github-issue-triage
Read, analyze, and draft high-signal GitHub issue responses from bounded provider evidence without silently mutating the repository.
reset-epic
Reset an epic's test data — close PRs, delete branches, reopen issues, revert code.
gitlab_read
Read access: projects, issues, MRs, files, pipelines, members.