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.eval)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/plan-next.eval"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/plan-next.eval.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.1 | $0.00000 | $0.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
plan-next.eval 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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval: /plan-next
Purpose
Analyzes the current repository state (git status, recent commits, open issues, existing plans) and recommends the next logical action. Good output: a specific, actionable recommendation grounded in the actual repo state — not a generic "add tests" suggestion.
Fixtures
None — operates on the current repository state.
Test Scenarios
S1: Repo with no open plan
Setup: Ensure no IMPLEMENTATION_PLAN.md exists in the repo root.
Invocation: /plan-next
Must:
- Reads recent git log, git status, and project structure
- Produces a recommendation for the next action
- Recommendation is specific (references actual files, commands, or issues)
- Provides a rationale for why this is the next action
Should:
- If recent commits suggest a feature in progress, recommends continuing or testing it
- If documentation is outdated relative to recent commits, recommends updating it
Must NOT:
- Recommend an action already reflected in recent commits as "done"
- Give the same recommendation regardless of repo state (must be context-aware)
S2: Repo with completed IMPLEMENTATION_PLAN.md
Setup: Copy fixtures/plans/implementation-plan.md to repo root and manually set all STATUS markers to done.
Invocation: /plan-next
Must:
- Detects that the plan is complete
- Does not recommend implementing an already-complete plan
- Recommends something appropriate for "plan complete" state (e.g., bump version, clean up, create PR)
S3: Repo with uncommitted changes
Setup: Modify a file and leave it uncommitted.
Invocation: /plan-next
Must:
- Notes the uncommitted changes in its analysis
- May recommend committing or completing the in-progress work before starting something new
S4: Read-only behavior
Must:
- Does not create any files
- Does not make git commits
- Analysis is in-conversation only
Rubric
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.
- 8d ago First seen · 81 lines · 0 tokens per session scan A 55fe4ba81f16
plan-next.eval is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 522 tokens. 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
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.