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 drn/dots --skill prioritizegit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/prioritize)<a href="https://agentmods.dev/skills/drn/dots/prioritize"><img src="https://agentmods.dev/badge/skills/drn/dots/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/drn/dots/prioritize"><img src="https://agentmods.dev/badge/skills/drn/dots/prioritize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00994 |
| Opus 5.5 | $0.00010 | $0.00398 |
| Sonnet 5.5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00099 |
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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Prioritization
Score and rank a list of work items using the RICE framework, then produce a prioritized backlog ready for sprint planning.
Arguments
$ARGUMENTS- Required: list of items to prioritize, OR a path to a file containing them, OR "backlog" to pull from git issues/PRs
If no arguments provided, ask the user what items to prioritize.
Context
- Repo: !
git rev-parse --show-toplevel 2>/dev/null | grep -oE '[^/]+$' | head -1 - Open issues: !
gh issue list --limit 20 --state open 2>/dev/null | head -20 - Open PRs: !
gh pr list --limit 10 --state open 2>/dev/null | head -10
Instructions
Step 1: Gather Items
Parse the input into a list of discrete work items. Each item needs:
- Title: short description
- Source: where it came from (user input, issue #, PR #, etc.)
If $ARGUMENTS is "backlog", pull from open GitHub issues and PRs.
If fewer than 3 items, ask the user if they want to add more -- RICE works best with 5+ items to compare.
Step 2: Score Each Item (RICE)
For each item, estimate:
| Factor | Scale | How to Estimate |
|---|---|---|
| Reach | Number of users/devs affected per quarter | Ask: who benefits? How many? |
| Impact | 0.25 (minimal), 0.5 (low), 1 (medium), 2 (high), 3 (massive) | Ask: how much does this move the needle? |
| Confidence | 50%, 80%, or 100% | How certain are these estimates? Use 80% as default. |
| Effort | Person-days (0.5 = half day, 1 = one day, etc.) | How long to implement, test, and ship? |
RICE Score = (Reach x Impact x Confidence) / Effort
When estimating, be conservative:
- Default Confidence to 80% unless there's strong evidence either way
- Round Effort UP (optimistic estimates are the #1 cause of missed deadlines)
- If you can't estimate Reach, ask the user -- don't guess
Step 3: Classify (MoSCoW)
After scoring, classify each item:
- Must -- blocking other work or critical for users. Non-negotiable.
- Should -- high value, should be in this sprint if capacity allows.
- Could -- nice to have. Only if there's leftover capacity.
- Won't -- explicitly out of scope. Saying "won't" prevents scope creep.
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 · 104 lines · 24 tokens per session scan A 43c793a725bf
prioritize is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 994 once invoked, about $0.0001 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…