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.
git clone --depth 1 https://github.com/sequenzia/claude-pluginsWrote 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/commands/sequenzia/claude-plugins/next)<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/next"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/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.
<a href="https://agentmods.dev/commands/sequenzia/claude-plugins/next"><img src="https://agentmods.dev/badge/commands/sequenzia/claude-plugins/next.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.00011 | $0.00699 |
| Opus 5.5 | $0.00004 | $0.00280 |
| Sonnet 5.5 | $0.00002 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
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 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suggest the best tasks to work on next based on priority, complexity, and dependency analysis.
Arguments:
count(optional): Number of recommendations (default: 5)project-name(optional): Project name if multiple task files exist
Process
-
Locate task file
- Search for
tasks/*.tasks.jsonfiles - Use specified project or prompt if multiple exist
- Search for
-
Filter eligible tasks
- Status is "not_started" or "in_progress"
blocked_byarray is empty (no incomplete dependencies)
-
Score and rank tasks
Scoring algorithm:
score = (priority_weight * 100) + (blocking_weight * 50) + complexity_bonus Priority weights: - critical: 4 - high: 3 - medium: 2 - low: 1 Blocking weight: - Number of tasks this task blocks (unblocks others faster) Complexity bonus (quick wins): - XS: +15 - S: +10 - M: +5 - L: +0 - XL: -5 -
Generate recommendations
Output Format
# Next Task Recommendations
**Project:** <project-name>
**Available tasks:** X (of Y total)
## Top Recommendations
### 1. TASK-XXX: <title>
**Score:** 450 | **Priority:** critical | **Complexity:** S
<brief description>
**Why recommended:**
- Critical priority (highest urgency)
- Blocks 3 other tasks
- Small complexity (quick win)
**Acceptance criteria:**
- [ ] Criterion 1
- [ ] Criterion 2
---
### 2. TASK-YYY: <title>
**Score:** 380 | **Priority:** high | **Complexity:** M
<brief description>
**Why recommended:**
- High priority
- Blocks 2 other tasks
- Unlocks Phase 2 work
---
### 3. TASK-ZZZ: <title>
**Score:** 320 | **Priority:** high | **Complexity:** XS
<brief description>
**Why recommended:**
- High priority
- Extra small complexity (very quick win)
---
(continue for requested count)
## Summary
| Rank | Task | Priority | Complexity | Blocks | Score |
|------|------|----------|------------|--------|-------|
| 1 | TASK-XXX | critical | S | 3 | 450 |
| 2 | TASK-YYY | high | M | 2 | 380 |
| 3 | TASK-ZZZ | high | XS | 0 | 320 |
## Quick Actions
- View task details: `/mission-control:show TASK-XXX`
- Mark complete when done: `/mission-control:complete TASK-XXX`
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 · 119 lines · 0 tokens per session scan A 3afb31cf9640
next is a command published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 699 once invoked, about $0.0000 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.