A command for reviewing open GitHub issues, which are tracked reports or tasks in a code repository, and ordering them by importance and dependencies. Dependencies are relationships where one task must be completed before another can start.

Use it to fetch open issues, inspect their relationships, and identify the highest-value work that is not blocked.

It helps turn a long, unstructured issue list into work that can be acted on first. It accounts for blocked tasks, labels, and related issue information.

How jayminwest/kotadb configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jayminwest/kotadb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jayminwest/kotadb/develop/.claude/commands/issues/prioritize.md

Clone the repo

git clone --depth 1 https://github.com/jayminwest/kotadb

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/jayminwest/kotadb/prioritize/github.svg)](https://agentmods.dev/commands/jayminwest/kotadb/prioritize)

Your own site

<a href="https://agentmods.dev/commands/jayminwest/kotadb/prioritize"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jayminwest/kotadb/prioritize"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/prioritize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,510 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.01510
Opus 5.5	$0.00000	$0.00604
Sonnet 5.5	$0.00000	$0.00302
Haiku 4.5	$0.00000	$0.00151

Measured 1mo ago against content hash 591ee3156900, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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.

.claude/commands/issues/prioritize.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Prioritize Open GitHub Issues

Template Category: Structured Data

Analyze and prioritize open GitHub issues using relationship-aware dependency management. This command helps identify the highest-value unblocked work based on dependencies, labels, and strategic alignment.

Steps

Sync repo state
- git fetch --all --prune
- git pull --rebase (ensure you have latest issue metadata)
Fetch all open issues

Source: GitHub API

gh issue list --limit 100 --state open --json number,title,labels,body,createdAt,updatedAt

Filter options:

Filter by assignee: --assignee @me or --assignee <username>
Filter by labels: --label "component:backend"

Parse relationship metadata

Parse Issue Bodies (GitHub API)

Review issue bodies for ## Issue Relationships section (see .claude/commands/docs/issue-relationships.md)
Extract relationship types:
- Depends On: Issues that MUST be completed before work can start (blockers)
- Related To: Issues providing context or sharing technical concerns
- Blocks: Issues waiting on current work to complete
- Supersedes: Issues that replace or deprecate previous work
- Child Of: Issues that are part of larger epics
- Follow-Up: Planned next steps after current work completes
Check corresponding spec files in .claude/.cache/specs/ for additional relationship context
Use gh issue view <number> to inspect individual issues for relationship details

Build dependency graph

GitHub API (manual graph building)

Identify unblocked issues (no unresolved "Depends On" references)
Identify high-leverage issues (blocking multiple downstream tasks via "Blocks" relationships)
Identify isolated issues (no dependencies, safe for parallel execution)
Check if "Depends On" issues are closed/merged before marking an issue as unblocked

Apply prioritization strategy
- Label-based priority:
  - priority:critical > priority:high > priority:medium > priority:low
- Effort-based quick wins:
  - Prefer effort:small for quick wins when priority is equal
  - Balance high-priority large efforts with small quick wins
- Strategic alignment:
  - Issues with Child Of relationships to active epics
  - Issues referenced in recent project discussions or OKRs
- Unblocked status:
  - ONLY recommend issues with no unresolved dependencies
  - Verify "Depends On" issues are closed before recommending

Read the full file on GitHub · 167 lines

Changes

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 · 167 lines · 0 tokens per session scan A 591ee3156900

Subscribe to this mod's changes

prioritize is a command published in the GitHub repository jayminwest/kotadb (100 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,510 tokens. 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.

Claude Code Project management ai-tools mcp

kotadb: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Prioritize Open GitHub Issues

Steps

What this file has done since we first saw it

Other commands, from other repositories

sprint

workflow-design

speckit.companion.implement

update-counts

speckit.companion.living-move

camp-init