Borrowing it
Nothing to install: this file belongs to MinistryPlatform-Community/MPNext. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MinistryPlatform-Community/MPNext/main/.claude/commands/audit-deps.mdgit clone --depth 1 https://github.com/MinistryPlatform-Community/MPNextWrote 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/ministryplatform-community/mpnext/audit-deps)<a href="https://agentmods.dev/commands/ministryplatform-community/mpnext/audit-deps"><img src="https://agentmods.dev/badge/commands/ministryplatform-community/mpnext/audit-deps/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/ministryplatform-community/mpnext/audit-deps"><img src="https://agentmods.dev/badge/commands/ministryplatform-community/mpnext/audit-deps.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.00015 | $0.04294 |
| Opus 5.5 | $0.00006 | $0.01718 |
| Sonnet 5.5 | $0.00003 | $0.00859 |
| Haiku 4.5 | $0.00002 | $0.00429 |
Grade A, and why
audit-deps 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 28d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit & Upgrade
Perform a complete review of this project's dependencies: real vulnerability exposure, available updates, and — with approval where required — apply and verify the upgrades.
No Ministry Platform writes. This command touches only local dependencies (
node_modules,package.json,package-lock.json) and local report files. It never reads or writes MP data, so the MP Data Safety rule in CLAUDE.md is not triggered. If any step would touch MP, stop and ask.
Arguments
Parse $ARGUMENTS; default behavior when none are given is described in each phase.
| Flag | Effect |
|---|---|
| (none) | Full audit → auto-apply safe updates + verify → propose majors → ask before any major → offer branch+commit |
--report-only |
Read-only. Produce the report and the exact commands, change nothing. Skip phases 6–9. |
--majors-only |
Skip the safe-update pass; only research and propose major upgrades. |
--major <pkg> |
After the normal run, attempt that one major upgrade with the verify/revert protocol in phase 8. |
--no-verify |
Skip build/lint/test verification. Only honor this if the user passed it explicitly; say loudly in the report that nothing was verified. |
Autonomy contract
Know exactly what you may do without asking:
Allowed without asking
- Every read-only command (
npm ls,npm audit,npm outdated,npm view,git status,git diff). npm installwith no package argument (syncs the tree to the lockfile). If it changespackage-lock.json, regenerate it withnpm run deps:relockand check it withnpm run deps:verify— a bare Windowsnpm install/npm dedupemust never produce the committed lockfile (CLAUDE.md § Dependency Rule).npm updatewith no package argument — applies patch/minor updates inside the existing ranges. This is the phase 6 workhorse; it never editspackage.json.npm run deps:relock/npm run deps:verify— required after anynpm update.npm audit fixwithout--force.- Patch/minor bumps that stay inside the existing
^range. - Writing the report file and updating the known-issues file.
- Running
npm run build,npm run lint,npm run test:run.
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.
- 28d ago Changed · +10 lines 1988b08c298b
- 1mo ago First seen · 318 lines · 15 tokens per session scan A f859a7bd4dfc
audit-deps is a command published in the GitHub repository MinistryPlatform-Community/MPNext (14 stars, last pushed 7d ago), licensed MIT. It adds 15 tokens to every session and 4,294 once invoked, about $0.0001 per session on Opus 5.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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.