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 skills add tomzx/agents --skill prioritizegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/prioritize)<a href="https://agentmods.dev/skills/tomzx/agents/prioritize"><img src="https://agentmods.dev/badge/skills/tomzx/agents/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/tomzx/agents/prioritize"><img src="https://agentmods.dev/badge/skills/tomzx/agents/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.00030 | $0.00457 |
| Opus 5 | $0.00015 | $0.00229 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
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 6d 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.
What it actually says
Prioritize
Scores and ranks work so sequencing is transparent and debatable rather than asserted. Uses RICE (Reach x Impact x Confidence / Effort) or WSJF (Cost of Delay / Job Size), recording the inputs so the ranking can be challenged and re-run when estimates change.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. roadmap.mdandgoals.md; a backlog of items to rank.
Steps
- Choose the framework. RICE suits discovery-stage ranking; WSJF suits time-critical sequencing where delay has a cost.
- For each item, estimate the framework's inputs explicitly (reach, impact, confidence, effort; or cost-of-delay and job size). Record the number and a one-line justification.
- Compute the score and rank.
- Sanity-check the ranking against strategic fit and dependencies. If the top item depends on a lower item, note the dependency and reorder.
- Separate "do" from "consider" vs. "cut": the cut list is as important as the do list. A backlog that never shrinks is not prioritized.
- Write a prioritized backlog to
.pdlc/context/roadmap.md(updated Now/Next/Later) or to the initiative directory for initiative-scoped work.
Output Format
A ranked table with scores and input justifications, plus the explicit cut list. Update the roadmap's Now/Next/Later to reflect the ranking.
Outcome
If $OUTCOME_YAML is set, emit verdict: ranked.
Completion Checklist
- Framework chosen and stated
- Every scored item has its inputs recorded with a justification
- Dependencies reflected in the final order
- A cut list exists (items explicitly not doing)
Next Step
Run the Strategy gate via make-decision. On proceed, load write-prd to begin Define.
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.
- 6d ago First seen · 43 lines · 30 tokens per session scan A 8f5528f8f168
prioritize is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 457 once invoked, about $0.0002 per session on Opus 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.