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 agentmods add commands/jayminwest/kotadb/prioritizegit clone --depth 1 https://github.com/jayminwest/kotadbWrote 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/commands/jayminwest/kotadb/prioritize)<a href="https://agentmods.dev/commands/jayminwest/kotadb/prioritize"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/prioritize.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01510 |
| Opus 5 | $0.00000 | $0.00755 |
| Sonnet 5 | $0.00000 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
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 5d 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 — 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 --prunegit 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 @meor--assignee <username> - Filter by labels:
--label "component:backend"
- Parse relationship metadata
Parse Issue Bodies (GitHub API)
- Review issue bodies for
## Issue Relationshipssection (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:smallfor quick wins when priority is equal - Balance high-priority large efforts with small quick wins
- Prefer
- Strategic alignment:
- Issues with
Child Ofrelationships to active epics - Issues referenced in recent project discussions or OKRs
- Issues with
- Unblocked status:
- ONLY recommend issues with no unresolved dependencies
- Verify "Depends On" issues are closed before recommending
- Label-based priority:
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.
- 5d ago First seen · 167 lines · 0 tokens per session scan A 591ee3156900
prioritize is a command published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo 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.
Other commands, from other repositories
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
synthesise-reviews
Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.