Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AleksandarBisevac/claude-plugins/plugin install auditWrote 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/aleksandarbisevac/claude-plugins/next)<a href="https://agentmods.dev/commands/aleksandarbisevac/claude-plugins/next"><img src="https://agentmods.dev/badge/commands/aleksandarbisevac/claude-plugins/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.1 | $0.00032 | $0.00517 |
| Opus 5 | $0.00016 | $0.00259 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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 6d 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.
What it actually says
/audit:next — execute the next ready task
Read ${CLAUDE_PLUGIN_ROOT}/reference/orchestrator.md and
${CLAUDE_PLUGIN_ROOT}/reference/manifest-conventions.md first.
If $ARGUMENTS contains --dry-run: follow the orchestrator's Dry-run / preview section —
show the next ready task and what would run, and STOP without mutating.
Otherwise run the full preflight (steps 1–5, including acquiring the lock) and emit Progress output.
- Print the entry view first, verbatim:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/status/audit-status.py" <manifestPath>— it names every ready task, in order, with what the rest are waiting on. Do not re-tabulate it and do not re-derive the readiness rule by hand; the first entry under READY NOW is the task this command runs. - Find the first ready task (phase order, then task-id order) per the Readiness rule.
- If none is ready: the entry view's
waiting oncolumn already says why, per task — relay it rather than restating it. Release the lock and stop. - Otherwise run Execute the task (orchestrator), then follow Reporting — outcome + what is ready next. Release the lock.
Before that release, if the task did not reach done: the record of its gate has nothing
to ride out on. This command commits on success and only on success, so a run ending
blocked — or stopping on the infrastructure path — leaves the rows the gate just wrote
sitting in the working tree with nothing coming behind them to carry them.
${CLAUDE_PLUGIN_ROOT}/commands/run.md → What one run leaves behind states it in full:
which invocation becomes evidence, why a refused pointer is not a failure, and what
commit-audit-state.py may and may not stage. It applies here unchanged — the two commands
differ in how the task is chosen and in nothing else.
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.
- 6d ago First seen · 36 lines · 32 tokens per session scan A 3056c9a737c9
next is a command published in the GitHub repository AleksandarBisevac/claude-plugins (4 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 517 once invoked, about $0.0002 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
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
history
List past OCR review sessions.
overlay-apply
Apply NIST 800-53 overlays (FedRAMP, DoD, Privacy, etc.) to existing baselines.
sdlc
Master orchestrator for the complete 5-phase SDLC pipeline. Runs all phases sequentially with approval gates and handoffs between each phase. Organizes artifacts into handoffs/, docs/, and projects/ directories.
pillar-guidance
Deep dive guidance on DORA's 5 pillars and implementation requirements.