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/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/plan-next)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/plan-next"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/plan-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/davistroy/claude-marketplace/plan-next"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/plan-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.00008 | $0.02671 |
| Opus 5 | $0.00004 | $0.01336 |
| Sonnet 5 | $0.00002 | $0.00534 |
| Haiku 4.5 | $0.00001 | $0.00267 |
Grade A, and why
plan-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 9d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Step Analysis
Analyze the current state of this repository and recommend the single highest-priority next action. This command is plan-aware, git-aware, and produces structured output with clear rationale.
Input Validation
No Arguments Required: This command takes no arguments.
If extra arguments are provided, they are ignored.
Before proceeding, verify:
- This is a valid git repository (
.git/directory exists) - Key project files are accessible (at minimum, one of: README.md, CLAUDE.md, or source files)
- The repository has meaningful content (not an empty init)
If the repository is empty or inaccessible, stop and report:
Error: Cannot analyze repository
The repository appears to be empty or inaccessible. Ensure you are in the
root of a git repository with at least some committed content.
Instructions
Analysis Process
Execute the following steps in order. Each step feeds into the decision logic below.
Step 1: Check for Active Plans
Search for planning artifacts in the repository root:
- IMPLEMENTATION_PLAN.md — Read it if found. Identify:
- Total phases and which phase is current
- The next
PENDINGwork item (by phase order) - Any
IN_PROGRESSitems (these take priority — they represent interrupted work) - Overall completion percentage (count COMPLETE vs total items)
- RECOMMENDATIONS.md — Read it if found. Note:
- Whether recommendations exist that have no corresponding implementation plan
- Any items marked as Critical priority
- PROGRESS.md or TODO.md — Read if found. Note any tracked items.
- Open GitHub Issues — Run
gh issue list --limit 10 --state open(ifghis available). Note count and any high-priority labels.
Record what was found and what was not.
Step 2: Check Git State
Run these commands and record the results:
git status --short— Check for uncommitted changes (staged, unstaged, untracked)git branch --show-current— Get current branch namegit log --oneline -5— Get recent commit messages for contextgit stash list— Check for stashed changesgh pr list --author @me --state open --limit 5— Check for open PRs (ifghavailable)
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.
- 9d ago First seen · 266 lines · 8 tokens per session scan A 890a6eb79455
plan-next is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 2,671 once invoked, about $0.0000 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
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.