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/p4-docsgit 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/p4-docs)<a href="https://agentmods.dev/commands/jonase47/ccpr/p4-docs"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p4-docs.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.01354 |
| Opus 5 | $0.00000 | $0.00677 |
| Sonnet 5 | $0.00000 | $0.00271 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
p4-docs 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p4-docs – README, Contributing Guide & Project Structure Documentation
Creates the foundational project documentation: a meaningful README, a contributing guide, and documentation of the project structure. The result is a documentation base that quickly onboards new developers and bindingly establishes standards.
Argument: $ARGUMENTS = [Documentation focus, e.g. "README", "Contributing", "API Docs", "Onboarding"]
If provided: Focus the elaboration on the named documentation area. If not provided: Create all core documents (README.md, CONTRIBUTING.md) in full. If any project context is missing, ask for the project name and tech stack.
Execution
1. Read Context
Read the following files (if available):
- CONCEPT.md (project description, value proposition)
- TECH_STACK.md (technologies for README badges and setup guide)
- INFRASTRUCTURE.md (CI/CD, deployment for developer documentation)
- ARCHITECTURE.md (explain project structure)
- SETUP_LOG.md (what was set up in
/p4-setup?) - TEST_STRATEGY.md (test guide for contributing guide)
- SECURITY.md (security guidelines for contributing guide)
2. Delegation to Tech-Writer Agent (Lead)
Delegate the documentation creation to the tech-writer agent:
Create the project documentation. Focus (if provided): $ARGUMENTS Context from all project documents: [Insert project name, description, tech stack, setup steps]
A. README.md Create a complete README with the following sections:
- Header: Project name, short description (1–2 sentences), status badges (CI, coverage, license)
- What is [Project Name]?: Value proposition in 3–5 sentences for developers
- Features: Most important features as a short list
- Tech Stack: Overview of technologies used with links
- Prerequisites: What needs to be installed? (Node.js, Docker, etc. with versions)
- Quick Start: Step-by-step guide for local setup (copy-paste ready)
- Development: Important commands (start dev, tests, lint, build, migrations)
- Project Structure: Directory tree with short explanations
- Tests: How to run tests, what is tested
- Deployment: Short explanation of the deployment process
- Contributing: Link to CONTRIBUTING.md
- License: License information
B. CONTRIBUTING.md Create a complete contributing guide with:
- Welcome: Short introduction stating what contributions are welcome
- Setting Up the Development Environment: More detailed than README, for external contributors
- Branch Strategy: Which branches exist, how are they named?
- Commit Convention: Conventional Commits with examples (feat, fix, docs, test, refactor...)
- Pull Request Process: How is a PR created? What is checked in review?
- Code Style & Linting: Which standards apply? Which tools enforce them?
- Test Requirements: What must be tested before a PR is merged?
- Security Guidelines: How are security findings reported (responsible disclosure)?
- Definition of Done: When is a change considered complete?
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 · 110 lines · 0 tokens per session scan A 0b3c1030de3c
p4-docs 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 1,354 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…