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 skills/flurdy/agent-skills/nextnpx skills add flurdy/agent-skills --skill nextgit clone --depth 1 https://github.com/flurdy/agent-skillsWrote 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/flurdy/agent-skills/next)<a href="https://agentmods.dev/skills/flurdy/agent-skills/next"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/next.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.00028 | $0.05142 |
| Opus 5 | $0.00014 | $0.02571 |
| Sonnet 5 | $0.00006 | $0.01028 |
| Haiku 4.5 | $0.00003 | $0.00514 |
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 4d 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 — 414 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.
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
/landscapefirst — 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 safe # Same but exclude services with in-progress beads
/next sprint # Same, enriched with Jira sprint and sorted by sprint bucket
/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 fix it
/next <bead-id> # Start working on specific bead
/next <repo>:<bead-id> # Start a bead whose ID exists in several workspace stores
What This Skill Does
-
Find Ready Work
- Run the
next-bdcollector to get open, unblocked tasks - At a valid project-workspace root, collect the root and every registered repository with a usable Beads store
- Exclude
in_progressbeads as tracker claims; session activity remains unverified - Show current in-progress tracker claims with repository identity (for awareness, not selection)
- Run the
-
Rank by Suitability
- Apply priority ranking algorithm (see below)
- Bugs generally rank higher than features at same priority
- Epics rank lower (they represent larger work)
-
Present Options
- Show top 5 candidates with key details
- Include: ID, title, priority, type, labels (services/tags), age
- Ask user to pick or provide different criteria
What ships with it
6 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.
- 4d ago First seen · 414 lines · 28 tokens per session scan A 6414d2f9addd
next is a skill published in the GitHub repository flurdy/agent-skills (7 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 5,142 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…