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/p3-securitygit 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/p3-security)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-security"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-security.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.00983 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
p3-security 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 today.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-security – Security Architecture, Threat Model & Auth Concept
Creates the complete security architecture: threat model, auth concept, data security, API security and developer checklist. Each area is its own sub-skill.
Argument: $ARGUMENTS = [Focus, e.g. "Auth", "API Security", "Data Encryption"]
If provided: Passed through to the sub-skills. If not provided: All sub-skills run sequentially.
Flow
0. Ensure Sub-Index Exists
Make sure docs/architecture/SECURITY.md exists as a sub-index with the standard header (Status / Last Updated / Key Decisions / Open Risks / Detail Files / Gate Notes — see ~/.claude/docs/PROJECT_PHASES.md). If missing, create it with empty placeholders. The five p3-sec-* sub-skills below each refresh their own row in this sub-index's Detail Files table.
1. STRIDE Threat Model
/p3-sec-threats $ARGUMENTS – Analyzes the system according to the STRIDE model.
2. Auth & Authorization Concept
/p3-sec-auth $ARGUMENTS – Defines auth method, roles and session management.
3. Data Security
/p3-sec-data $ARGUMENTS – Encryption (transit/rest), secrets management, backups.
4. API Security
/p3-sec-api $ARGUMENTS – Input validation, rate limiting, CORS, security headers.
5. Developer Checklist
/p3-sec-checklist – Concrete security checklist for phase 5.
6. Roll Up Sub-Index to Phase Index
After all p3-sec-* sub-skills have run, summarise the security sub-index into the phase index docs/architecture/ARCHITECTURE.md:
- Add an entry in the phase-index Detail Files table for
[SECURITY.md](SECURITY.md)(the sub-index itself), statuscompleteonce all five sub-skill rows inSECURITY.mdarecomplete. - Lift the headline security decisions (auth method, encryption strategy, top critical threat) into the phase-index Key Decisions.
- Lift any unresolved Critical/High threats from
THREATS.mdinto the phase-index Open Risks.
7. Final HANDOVER Update (Orchestrator-owned)
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.
- today First seen · 68 lines · 0 tokens per session scan A faf1c487e75f
p3-security 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 983 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
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
pseo-init
Use when: kullanıcı "yeni proje", "init", "proje kur", "yeni domain ekle", "scaffold" gibi ifadeler kullanır ya da /pseo-init çağırırsa. Also use when: portföye yeni bir SEO projesi alındı, projects/{slug}/ klasörü ve project.config.json dosyasının schemaya uygun ilk hâli üretilecek; brief'te slug + domain + market…
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.
forge-context-status
Report on current context window usage, cache health, and compaction recommendation. Read-only — does not compact.
CLAUDE
Each subdirectory is one engine verb dispatched by ../cli/cli.ts: / .ts exports a pure handler that resolves the vault, does its work through ../core/ primitives, and returns its own typed report. Commands stay thin — they compose core checks and builders; they do not reimplement them. The canonical output schema is…