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/jonase47/ccpr/p6-audit-depsgit clone --depth 1 https://github.com/jonase47/ccprWrote 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/jonase47/ccpr/p6-audit-deps)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-audit-deps"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-audit-deps.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.00000 | $0.00787 |
| Opus 5 | $0.00000 | $0.00394 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
p6-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 yesterday.
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.
This is a copy
86% identical to p6-audit-config — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-audit-deps – Dependency Check
Checks all dependencies for known vulnerabilities (CVEs), outdated packages, and maintenance status.
Argument: $ARGUMENTS = [package manager/area]
If provided: Focus on the specified area. If not provided: Check all dependency files.
Prerequisites
- Dependency files present (package.json, requirements.txt, go.mod, etc.)
Agent
- Type: security-master
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- Dependency files: package.json, lock files (direct dependencies only)
- From TECH_STACK.md: Technologies in use
Prompt Template
Goal: Dependency check – identify known vulnerabilities and outdated packages
Dependencies: [inline from package.json / requirements.txt / etc.]
Output Format: Table with max. 15 findings:
# Package Version CVE/Issue CVSS Recommendation Summary: X critical, Y high, Z outdated
Constraints:
- Dependency analysis ONLY – no code review
- Priority: CVSS >= 7.0
- Also report outdated packages without active maintenance
- For zero dependencies: a brief confirmation is sufficient
Orchestrator Checkpoint
- All dependency files checked?
- Critical CVEs with concrete update recommendation?
Write Detail File
Write the result to docs/quality/audit_deps.md (overwrite). Frontmatter:
---
phase: P6
subskill: audit-deps
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Findings (CVE table), ## Severity Summary.
Update Sub-Index
Update docs/quality/AUDIT.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[audit_deps.md](audit_deps.md)with statuscomplete. - Lift any unpatched Critical CVE into Open Risks.
Handover Epilogue
Before writing. docs/HANDOVER.md is capped — the file states its own limit in its header
(default: ≤5 KB / ~150 lines). Two rules follow from that, and neither is optional:
- Replace this command's previous epilogue block, do not append a second one. Stacking is what pushes the file over; one skill run has been measured adding 1021 B, ~20 % of the cap.
- If the file is already near its cap, shorten before you add. Reading the cap sentence is not
the same as measuring: check the actual size, and when there is no room, condense existing content
or hand the user
/cleanupinstead of growing the file further.
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.
- yesterday First seen · 87 lines · 0 tokens per session scan A b3319e5b6cf3
p6-audit-deps is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 787 tokens. A static security scan graded it A with 0 findings. It is 86% identical to p6-audit-config, differing in 55 lines, and is treated as a copy.
Other commands, from other repositories
sdd-implement
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.
wiki-tune
Tune wiki schema and conventions interactively.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].
approvals
Show the pending approval queue.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
agents
List all agent git worktrees and their branch / dirty / HEAD status.