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 LucasSantana-Dev/sharekit --skill next-prioritygit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/next-priority)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/next-priority"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/next-priority/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/lucassantana-dev/sharekit/next-priority"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/next-priority.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.00022 | $0.00973 |
| Opus 5.5 | $0.00009 | $0.00389 |
| Sonnet 5.5 | $0.00004 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
next-priority 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
next-priority
Choose the next action using evidence, not intuition.
Decision order
This list is the SINGLE canonical ranking (references/priority-rules.md holds PR-state interpretation detail, not a second ranking).
- Merge-ready PRs
- Release blockers
- Failing CI, flaky tests, or stale-base PRs blocking merges (stale-base = PR targets a branch already merged into default; retarget before it can ship)
- Security issues with a known safe fix
- Overdue date-gated commitments — "re-check X by " items from handoffs and memory whose date has passed (scan command in references/scan-commands.md)
- Small production-ready fixes or features
- Concrete tech debt slowing delivery
- Refactors justified by churn or repeated friction
- Deferred migrations or speculative work
If the picked action is irreversible or outward-facing (merge, deploy, publish,
history rewrite), the pick stands but execution follows the autonomy tiers in
~/.claude/standards/autonomy-tiers.md (ADR-0051) — this skill chooses, it does
not bypass gates.
Waiting for CI is never a priority
"Merge-ready PRs" (rank 1) means a PR whose checks have already passed and is mergeable now. A PR whose CI is still running is NOT merge-ready and NOT a priority — never pick "wait for / poll the PR's CI" as the next action. CI completion re-surfaces the PR via its own notification; until then, drop to the next actionable item and do real work. Sole exception: the next task is blocked on that exact code — it needs the in-flight branch's changes to proceed. Only then is the in-flight PR the gating item, and even then advance any independent work first. Idle-polling an in-flight PR is a priority-inversion.
Required evidence
Check, in order:
- active handoff
- overdue date-gated items (handoffs + memory date scan — see scan-commands.md)
- active plan
- current branch and open PRs
- CI status on the current branch / HEAD
- open review comments or blocking issues
- recent commits and working tree state
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 89 lines · 22 tokens per session scan A f6c6e91689cd
next-priority is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 973 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-09-03.
Other skills, from other repositories
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
ulw-execute
Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.