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-datagit 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-data)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-sec-data"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-sec-data.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.00867 |
| Opus 5 | $0.00000 | $0.00434 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
p3-sec-data 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-sec-data – Data Security Concept
Defines encryption (transit/rest), secrets management and backup security.
Argument: $ARGUMENTS = [Focus, e.g. "Encryption", "Secrets", "Backup"]
If provided: Deep-dive the named area. If not provided: Create complete data security concept.
Prerequisites
- ARCHITECTURE.md and threat model exist
- DATA_MODEL.md exists (if database is present)
Agent
- Type: security-master
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From SECURITY.md: Threat model (information disclosure rows)
- From DATA_MODEL.md: Data fields requiring protection (if available)
- From TECH_STACK.md: Database/hosting in use
Prompt Template
Goal: Define data security measures for the project.
Context: [inline from SECURITY.md, DATA_MODEL.md]
Output Format:
- Encryption in transit: TLS version, HSTS (1-2 sentences)
- Encryption at rest: Table | Data Field | Encryption | Method |
- Secrets management: where are secrets stored, how are they rotated?
- Backup security: encryption, retention
Constraints:
- ONLY data security, NO auth concept, NO API security
- Measures proportional to project risk
- Max. 8 encrypted fields in the table
Orchestrator Checkpoint
- All sensitive fields from DATA_MODEL.md covered?
- Secrets strategy concrete (not just "use a vault")?
Write Detail File
Write the result to docs/architecture/DATA_SECURITY.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: sec-data
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Encryption in Transit, ## Encryption at Rest (the field/encryption/method table), ## Secrets Management, ## Backup Security.
Update Sub-Index
Update docs/architecture/SECURITY.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[DATA_SECURITY.md](DATA_SECURITY.md)with statuscomplete. - Lift the secrets-management decision and any field that is not encrypted-at-rest despite being sensitive into Key Decisions / Open Risks of the sub-index.
- 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.
- yesterday First seen · 88 lines · 0 tokens per session scan A 58dab5bf33e8
p3-sec-data 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 867 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…