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-arch-componentsgit 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-arch-components)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-arch-components"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-arch-components.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.01208 |
| Opus 5 | $0.00000 | $0.00604 |
| Sonnet 5 | $0.00000 | $0.00242 |
| Haiku 4.5 | $0.00000 | $0.00121 |
Grade A, and why
p3-arch-components 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-arch-components – Component Diagram & Data Flows
Creates the system architecture overview with component diagram, responsibilities and data flows.
Argument: $ARGUMENTS = [Architecture style, e.g. "Monolith", "Microservices", "Single-File"]
If provided: Use the style as a starting point. If not provided: Recommend the most suitable style based on the context.
Prerequisites
- CONCEPT.md and FEATURES.md exist
- MVP.md defines the scope
Agent
- Type: system-architekt
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From CONCEPT.md: Project description, core mechanics
- From FEATURES.md: Must-Have features (short list)
- From VALIDATION.md: PoC findings (if available)
Prompt Template
Goal: Create component diagram and data flows for: $ARGUMENTS
Context: [inline from CONCEPT.md, FEATURES.md]
Output Format:
- Component diagram (ASCII art or Mermaid)
- Table: | Component | Responsibility | Dependencies |
- Data flows as numbered list
Constraints:
- ONLY architecture overview, NO tech stack, NO ADRs
- Max. 10 components
- External integrations only if mentioned in the context
Orchestrator Checkpoint
- Diagram covers all must-have features?
- No component without a clear responsibility?
Write Detail Files
The result can be written flat (single COMPONENTS.md) or as sub-index with per-component detail files, depending on size.
Choose Layout
| Condition | Layout |
|---|---|
| ≤6 components AND result fits in <20 KB | Flat: single COMPONENTS.md |
| ≥7 components OR result ≥20 KB | Sub-Index: lean COMPONENTS.md + components/ subfolder with one detail file per component |
Flat Layout (small architectures)
Write docs/architecture/COMPONENTS.md (overwrite if it exists). Frontmatter:
---
phase: P3
subskill: arch-components
kind: detail
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Component Diagram (ASCII or Mermaid), ## Component Responsibilities (the responsibilities/dependencies table), ## Data Flows (numbered list).
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 · 134 lines · 0 tokens per session scan A 68cbeeb47655
p3-arch-components 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,208 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
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
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…