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 commands/aleksandarbisevac/claude-plugins/phasegit clone --depth 1 https://github.com/AleksandarBisevac/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/aleksandarbisevac/claude-plugins/phase)<a href="https://agentmods.dev/commands/aleksandarbisevac/claude-plugins/phase"><img src="https://agentmods.dev/badge/commands/aleksandarbisevac/claude-plugins/phase.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.00075 | $0.04554 |
| Opus 5 | $0.00037 | $0.02277 |
| Sonnet 5 | $0.00015 | $0.00911 |
| Haiku 4.5 | $0.00007 | $0.00455 |
Grade B, and why
phase scanned grade B with 1 finding 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 5d 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.
Tells the agent never to refusemediumAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
then follow the answer. Never resolve it silently and never refuse outright — both Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit:phase — add a phase, run it, order it, or close it
Read ${CLAUDE_PLUGIN_ROOT}/reference/orchestrator.md and
${CLAUDE_PLUGIN_ROOT}/reference/manifest-conventions.md first.
0. Which verb — read off $ARGUMENTS, before the manifest is
The FIRST token decides, and the reserved words are add, retarget, priority and cancel.
Any other first token is a phase id, and the command is the run form below — the
shape this command has always had, unchanged.
Lexical, never inferred from the plan. Deciding the verb by asking the manifest whether the first token happens to name a phase would give one command line two meanings on two machines, and the argument has to be read before the manifest is even located. So the rule is about the word, and it is the same word everywhere.
The one collision, and it is asked rather than guessed. phase.id is a free-text
string in ${CLAUDE_PLUGIN_ROOT}/schema/audit-plan.schema.json — P<n> / BF<n> is
the allocation convention (conventions → ID allocation), not a shape the validator
holds — so a hand-written manifest MAY carry a phase whose id is one of the reserved
words. Once the manifest is read, if it names a phase whose id equals the word you
dispatched on, STOP: print both readings and ask (AskUserQuestion) which was meant,
then follow the answer. Never resolve it silently and never refuse outright — both
readings stay reachable, one question apart. There is no arity exception either: three
tokens are no more decidable than one when a rule has a carve-out nobody remembers.
Run a phase — <phaseId> [--dry-run]
$ARGUMENTS = the phase id (plus optional --dry-run).
If --dry-run is present: follow the orchestrator's Dry-run / preview section instead —
read-only preflight, print the plan (branch, ready tasks, parallel groups, merge target), and STOP.
The branch and the merge target both come from
resolve-branch.py <manifestPath> --phase <phaseId> — never composed here — and when the
merge target is not meta.developmentBranch, the plan says so: signing off there does not put
the work on the development branch.
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.
- 5d ago First seen · 278 lines · 75 tokens per session scan B b957b6ada6b0
phase is a command published in the GitHub repository AleksandarBisevac/claude-plugins (4 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 4,554 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (tells the agent never to refuse). 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.