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-apigit 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-api)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-sec-api"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-sec-api.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.00865 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
p3-sec-api 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-sec-api – API Security Requirements
Defines input validation, rate limiting, CORS and security headers.
Argument: $ARGUMENTS = [Focus, e.g. "CORS", "Rate Limiting", "Headers"]
If provided: Deep-dive the named area. If not provided: Create complete API security requirements.
Prerequisites
- ARCHITECTURE.md exists
- API endpoints known (from DATA_MODEL.md or API_SPEC.md)
Agent
- Type: security-master
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From ARCHITECTURE.md: API components and data flows
- From DATA_MODEL.md: API endpoints (if available)
- From TECH_STACK.md: Backend framework
Prompt Template
Goal: Define API security requirements.
Context: [inline from ARCHITECTURE.md, DATA_MODEL.md]
Output Format:
- Input validation: strategy (whitelist/blacklist), sanitization
- Rate limiting: Table | Endpoint Type | Limit | Time Window |
- CORS: allowed origins, methods, headers
- Security headers: Table | Header | Value | Purpose |
Constraints:
- ONLY API security, NO auth concept, NO data encryption
- Max. 6 rate limit rules
- Max. 8 security headers
- If no API present: explicitly justify and keep section minimal
Orchestrator Checkpoint
- OWASP Top 10 API risks considered?
- Security headers complete (CSP, X-Frame-Options, etc.)?
Write Detail File
Write the result to docs/architecture/API_SECURITY.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: sec-api
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Input Validation, ## Rate Limiting, ## CORS, ## Security Headers.
Update Sub-Index
Update docs/architecture/SECURITY.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[API_SECURITY.md](API_SECURITY.md)with statuscomplete. - Note any OWASP Top-10-API risk that is NOT yet mitigated under 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.
- today First seen · 89 lines · 0 tokens per session scan A eb492f9a181b
p3-sec-api 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 865 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
experiment
Scaffold a new tracked experiment — create notebook, set up tracking, log baseline, define success criteria.
hypothesis
Generate hypotheses and define how to test them.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.