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/propose)<a href="https://agentmods.dev/commands/aleksandarbisevac/claude-plugins/propose"><img src="https://agentmods.dev/badge/commands/aleksandarbisevac/claude-plugins/propose.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.00059 | $0.01541 |
| Opus 5 | $0.00030 | $0.00771 |
| Sonnet 5 | $0.00012 | $0.00308 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
propose 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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit:propose — parked phases, materialized on demand
Proposals live in the manifest's top-level proposals[], OUTSIDE phases — a parked
phase is not yet a plan (the same shape bugs have: bugs[] → /audit:bug fix).
Each payload-bearing proposal carries the FULL synthesized phase (payload.phase,
tasks initialized per the new-task template), so materialize moves it into
phases[] without re-planning anything.
Proposal lifecycle: proposed → materialized | dropped.
$ARGUMENTS: first token is the subcommand. Unknown/empty → print usage and stop.
0. Conventions
Read ${CLAUDE_PLUGIN_ROOT}/reference/manifest-conventions.md FIRST. Resolve and read
the manifest. If it doesn't exist, stop and point to /audit:init.
After EVERY mutation: revalidate with
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/manifest/validate-manifest.py" <manifestPath> —
on findings, fix and re-run until clean.
materialize and drop hold the index lock (conventions → Concurrency lock)
around their writes — they mutate the phase directory and fileIndex; list is
read-only and never locks.
The rule is a script, not this file
list, materialize, drop and revive are one implementation, in
${CLAUDE_PLUGIN_ROOT}/scripts/manifest/materialize-proposal.py. The three writers
hold the index lock, revalidate before they write, and refuse rather than guess;
list is read-only and prints its own table. Do not re-derive any of it here —
the panel calls the same script and its Proposals tab reads the same rows, and two
readings of one rule are two answers the first time either is edited.
What stays YOURS is the conversation: printing what the script returns, asking the one question it deliberately will not ask itself, and reporting the handoff.
Subcommand: list
Read-only; no lock. Run it and print the output verbatim — the table is what the script prints, not a shape to reproduce from this file:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/manifest/materialize-proposal.py" \
<manifestPath> list [all]
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.
- 7d ago First seen · 127 lines · 59 tokens per session scan A ad2e1ffe8b33
propose is a command published in the GitHub repository AleksandarBisevac/claude-plugins (4 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 1,541 once invoked, about $0.0003 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.