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-sastgit 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-sast)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-audit-sast"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-audit-sast.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.00789 |
| Opus 5 | $0.00000 | $0.00394 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
p6-audit-sast 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-audit-sast – Static Code Analysis
Checks source code for injection vulnerabilities, insecure cryptography, secrets in code, and insecure error handling.
Argument: $ARGUMENTS = [module/file/entire codebase]
If provided: Focus SAST on the specified area. If not provided: Check the entire source code.
Prerequisites
- Source code present in src/
Agent
- Type: security-master
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- From src/: The code to be checked (affected files only)
- From SECURITY.md: Developer checklist (security-relevant points)
Prompt Template
Goal: Static code analysis (SAST) for: [area]
Code: [inline from src/]
Output Format: Table with max. 15 findings:
# Severity Category File:Line Finding Recommendation Categories: Injection, Cryptography, Secrets, Error Handling, Logging
Constraints:
- Static analysis ONLY – no runtime test, no pentest
- Focus on OWASP Top 10
- No style findings, security-relevant issues only
Orchestrator Checkpoint
- All source code files checked?
- Findings are specific (file + line)?
Write Detail File
Write the result to docs/quality/audit_sast.md (overwrite). Frontmatter:
---
phase: P6
subskill: audit-sast
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Findings (SAST table with file/line/severity), ## 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_sast.md](audit_sast.md)with statuscomplete. - Lift any High/Critical SAST finding 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 · 86 lines · 0 tokens per session scan A 11420486aac8
p6-audit-sast 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 789 tokens. 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-09-03.
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].
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.
approvals
Show the pending approval queue.