A command that examines open GitHub Issues and Seeds tasks, then recommends the next issues to tackle. It also compares them with the project's tests, lint checks, type checks, and code health.

Use it to prioritize all open work or focus on an area such as commands, storage, or templates.

It brings scattered priorities, dependencies, community interest, and current code quality into one decision. This makes it easier to choose work with the greatest practical value.

How jayminwest/seeds configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jayminwest/seeds. 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/seeds/main/.claude/commands/prioritize.md

Clone the repo

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

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/seeds/prioritize/github.svg)](https://agentmods.dev/commands/jayminwest/seeds/prioritize)

Your own site

<a href="https://agentmods.dev/commands/jayminwest/seeds/prioritize"><img src="https://agentmods.dev/badge/commands/jayminwest/seeds/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/seeds/prioritize"><img src="https://agentmods.dev/badge/commands/jayminwest/seeds/prioritize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2 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,116 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 92% copy Near-identical to another mod 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.00002	$0.01116
Opus 5.5	$0.00001	$0.00446
Sonnet 5.5	$0.00000	$0.00223
Haiku 4.5	$0.00000	$0.00112

Measured 1mo ago against content hash a3a2fc6c67e7, 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.

Origin

This is a copy

92% identical to prioritize — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/prioritize.md · 115 lines

How it starts

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

description

Analyze all open issues across GitHub Issues and Seeds, cross-reference with codebase health, and recommend the top ~5 issues to tackle next.

Argument: $ARGUMENTS — optional: a label or area to focus on (e.g., commands, store, templates). If empty, analyze everything.

gather-issues

Use the Task tool to spawn three parallel agents:

Agent A: GitHub Issues

Run gh issue list --state open --limit 50 --json number,title,author,labels,createdAt,updatedAt,body
For each issue, capture: number, title, labels, author, creation date, body summary
Note any issues with community engagement (comments, thumbs-up, external authors)

Agent B: Seeds Issues

Run sd list and sd ready
For each open issue, run sd show <id> to get full details
Capture: id, title, type, priority, status, description, dependencies/blockers
Build a dependency graph: which issues block which

Agent C: Codebase Health

Run bun test and capture pass/fail counts
Run bun run lint and capture error counts
Run bun run typecheck and capture error counts
Search for TODO, FIXME, HACK comments and count them
Check which source files lack test coverage (compare src/**/*.ts vs src/**/*.test.ts)
Summarize: is the codebase healthy, or are there quality issues that need attention

cross-reference

After all three agents complete:

Deduplicate: Match GitHub issues to Seeds issues that describe the same work (same title, overlapping description, related files)
Dependency mapping: Identify chains — issues that must be done before others can start
Cluster detection: Group related issues that could be tackled together (same subsystem, same theme, same files)
Staleness check: Flag issues that have been open a long time with no activity

scoring

For every unique issue (deduplicated), assess:

a. Impact

Does it fix a bug that blocks users?
Does it enable new capabilities or unblock other work?
How many other issues does it unblock (dependency graph)?
Does it affect external users (GitHub issues from community)?

Read the full file on GitHub · 115 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 · 115 lines · 2 tokens per session scan A a3a2fc6c67e7

Subscribe to this mod's changes

prioritize is a command published in the GitHub repository jayminwest/seeds (132 stars, last pushed 25d ago), licensed MIT. It adds 2 tokens to every session and 1,116 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to prioritize, differing in 8 lines, and is treated as a copy.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

dispatcher

Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…

Kanevry/session-orchestrator · 185 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

plc-project-status

Read .claude/skills/plc-project-status/SKILL.md and execute its official procedure. Target: $ARGUMENTS.

miyatti777/ai-plc · 14 tokens

seeds: Command for Claude Code