Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nick-pape/grackle/main/.claude/skills/backlog-prioritize/SKILL.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/backlog-prioritize)<a href="https://agentmods.dev/skills/nick-pape/grackle/backlog-prioritize"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/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/skills/nick-pape/grackle/backlog-prioritize"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/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.00038 | $0.00686 |
| Opus 5.5 | $0.00015 | $0.00274 |
| Sonnet 5.5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Prioritize — Suggested Issue Ordering
This skill fetches all open approved-for-grackle issues, filters out ones that already have a PR, and outputs a suggested priority ordering with rationale.
REPO="nick-pape/grackle"
Step 1: Fetch All Approved Issues
gh issue list -R $REPO --label "approved-for-grackle" --state open --limit 100 --json number,title,labels,body
Step 2: Find Issues That Already Have PRs
Check for open PRs that reference these issues (via branch name or body):
gh pr list -R $REPO --state open --limit 100 --json number,title,body,headRefName
Cross-reference: if a PR's body contains Closes #<N> / Fixes #<N>, or its branch name contains the issue number (e.g., nick-pape/295-unified), that issue is already in progress. Exclude it from the ordering.
Step 3: Classify and Sort
For each remaining issue, extract:
- Priority label:
priority:critical>priority:high> (unlabeled) >priority:low - Type:
bug>feature>refactor(bugs first — they degrade existing functionality) - Domain labels:
orchestration,web,server,powerline,cli - Dependencies: Read each issue body for references to other issues. If issue A mentions "depends on #B" or "requires #B first" or "after #B", A should come after B.
Sort by:
- Priority label (critical first)
- Type (bugs before features before refactors)
- Dependency ordering (blockers before dependents)
- Issue number (older issues first, as a tiebreaker)
Step 4: Identify Parallelizable Work
Group issues by domain (web, server, powerline, etc.). Issues in different domains with no dependency relationship can be worked on in parallel by different agents/environments.
Step 5: Output the Ordering
Present an ordered report using the following Markdown structure:
## Suggested Backlog Order
### Priority Tier 1 (Critical)
| # | Issue | Type | Domain | Why here |
|---|-------|------|--------|----------|
| 1 | #NNN — Title | feature | server | Critical priority, no dependencies |
### Priority Tier 2 (High)
...
### Priority Tier 3 (Normal)
...
### Parallelization Opportunities
- **Web track**: #X, #Y, #Z (can run concurrently with server track)
- **Server/orchestration track**: #A, #B, #C
### Excluded (already have PRs)
- #NNN — Title (PR #MMM)
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.
- 1mo ago First seen · 77 lines · 38 tokens per session scan A 4f7e62a226a2
backlog-prioritize is a skill published in the GitHub repository nick-pape/grackle (22 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 686 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
kanban-tasks
A task-board workflow for breaking work into cards and moving them through stages such as inbox, ready, doing, review, and done. It also includes a background service and a web interface for the board.
configure-coddy
Change Coddy's own configuration when the user asks for it: edit settings, providers, models, logging, permissions, or find, install, update, and remove MCP servers and skills. Stages UCI-style commands for config.yaml and commits only after the user confirms saving; MCP servers are entries of the mcp.json files. Load…
crossreview
Run when the user invokes /crossreview (or /crossreview:setup to choose the reviewers) or asks for a cross-review, a quorum review or a second opinion from other agents or models: fan a code review (uncommitted work, a branch, a commit range, files, a plan or a document) out to several console code agents (Claude…
rpa-init
Run when the user invokes /rpa-init or asks to onboard or warm up context on a repository. The agent studies code, reads documentation and test code, sets up the dev environment as the project expects, runs tests, and writes a short project report. No extra user brief is required.
rpa-gen-rules
Use when the user invokes /rpa-gen-rules or asks to create, refresh, audit, or synchronize project instructions such as root AGENTS.md, Cursor .cursor/rules, or Claude Code .claude/rules, especially when existing rule trees have drifted.
rpa-feat
Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build.