A task-selection tool that ranks ready Beads, which are tracked development tasks, across validated workspace stores. It can also start a selected task or filter the choices by situation.

Use it at the start of a work session, after finishing a task, or when choosing a task, quick win, or bug to tackle next.

It helps decide what to work on next when several tasks are available. The ranking uses task readiness and user preferences while preserving local task-store behavior.

next — Skill for Claude Code by flurdy/agent-skills

Install

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.

Any agent

npx skills add flurdy/agent-skills --skill next

Clone the repo

git clone --depth 1 https://github.com/flurdy/agent-skills

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/skills/flurdy/agent-skills/next/github.svg)](https://agentmods.dev/skills/flurdy/agent-skills/next)

Your own site

<a href="https://agentmods.dev/skills/flurdy/agent-skills/next"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/next/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/skills/flurdy/agent-skills/next"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/next.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 9,607 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Excessive Agency · line 8
Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.

Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.

How audits are shown

Origin original No closer match found 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.00034	$0.09607
Opus 5.5	$0.00014	$0.03843
Sonnet 5.5	$0.00007	$0.01921
Haiku 4.5	$0.00003	$0.00961

Measured yesterday against content hash d4215ed861f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

next 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 yesterday.

The scan reads SKILL.md. This mod also ships 13 executable files (pi/index.ts, pi/lease-selection.ts, scripts/collect.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/next/SKILL.md · 701 lines

How it starts

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

Next - Pick Your Next Bead

Help select the next bead to work on based on readiness and user preferences. Listing is read-only; the optional safe helper only observes and never claims. The user's selection (or explicit auto-pick mode) requests work on that one bead, not merely a tracker update. Claim once, show its full details and first step in visible commentary, then continue into that bead's appropriate workflow in the same turn. Do not ask for confirmation merely to start work after the selection. The tracker claim grants no additional authority; preserve the user's scope, each workflow's boundaries and all required approvals. Never select a second bead automatically.

When to Use

Starting a new work session
Finished a task and need to pick the next one
Want to see what's available to work on
Need help prioritizing between multiple options

Deciding between resuming a handoff and starting fresh? Run /landscape first — its **Next:** line weighs last session's live thread against fresh ready work. This skill is the "start fresh" branch of that decision; it still runs its own handoff check (see Resume awareness) before marking a bead in_progress.

Usage

/next                    # Show ready beads as a ranked table (same as `list`)
/next list               # Explicitly render the full ranked table, then ask which to pick
/next backlog            # Same, always including the P4 backlog table
/next safe               # Explicit source scope + advisory local Pi occupancy; separate unknowns
/next sprint             # Same, enriched with Jira sprint and sorted by sprint bucket
/next recover <repo>     # Check one unavailable store; confirm local startup, then retry once
/next task               # Auto-pick the next most suitable task and start it
/next quick              # Auto-pick an easy win (excludes busy services)
/next bug                # Auto-pick the next most important bug and claim it
/next <bead-id>          # Start working on specific bead
/next <repo>:<bead-id>   # Start a bead whose ID exists in several workspace stores

Read the full file on GitHub · 701 lines

Files

What ships with it

18 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.

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.

yesterday Changed · +64 lines · +1 tokens per session d4215ed861f2
4d ago Changed · +84 lines abf1a6546a82
9d ago Changed · +5 lines 1a62ec650b93
17d ago Changed · +33 lines 664bf0d076ce
19d ago Changed · +17 lines a8e70ff97763
20d ago Changed 398371d2e216
1mo ago Changed · +51 lines 26bc0022c656
1mo ago Changed · +18 lines · +5 tokens per session 91bcf6f2905b
1mo ago Changed · +15 lines 2341b5ec40b6
1mo ago First seen · 414 lines · 28 tokens per session scan A 6414d2f9addd

Subscribe to this mod's changes

next is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 9,607 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-31.

Project management agent-skills claude codex

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens