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-sec-checklistgit 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-sec-checklist)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-sec-checklist"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-sec-checklist.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.00857 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
p3-sec-checklist 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-sec-checklist – Developer Security Checklist
Creates a concrete checklist that every feature in phase 5 must fulfill.
Argument: $ARGUMENTS = not applicable
Always creates the complete checklist based on the security architecture.
Prerequisites
- SECURITY.md with threat model, auth concept, data security and API security
Agent
- Type: security-master
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From SECURITY.md: All previous sections (threat model, auth, data, API) – short version
- From TECH_STACK.md: Technologies in use (for tech-specific rules)
Prompt Template
Goal: Create developer security checklist for phase 5.
Security Architecture: [short version from SECURITY.md]
Output Format: Checklist with max. 15 items, grouped by:
- Input & Output (validation, encoding, sanitization)
- Auth & Session (if relevant)
- Data & Secrets (encryption, no plain text)
- Logging & Error Handling (do not log sensitive data)
- Forbidden Practices (eval, innerHTML, secrets in code, etc.)
Constraints:
- ONLY checklist, NO new analyses
- Every item must be concretely verifiable (yes/no)
- Adapted to the actual tech stack
Orchestrator Checkpoint
- Checklist covers all SECURITY.md sections?
- Items are verifiable (not vague)?
Write Detail File
Write the result to docs/architecture/CHECKLIST.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: sec-checklist
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Input & Output, ## Auth & Session, ## Data & Secrets, ## Logging & Error Handling, ## Forbidden Practices.
Update Sub-Index
Update docs/architecture/SECURITY.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[CHECKLIST.md](CHECKLIST.md)with statuscomplete. - Lift the existence of the checklist into Key Decisions of the sub-index (e.g.
- Developer security checklist ready for P5 → see CHECKLIST.md). - Do not edit
ARCHITECTURE.mddirectly.
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 · 87 lines · 0 tokens per session scan A e06d87941490
p3-sec-checklist 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 857 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…