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-techstackgit 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-techstack)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-arch-techstack"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-arch-techstack.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.00819 |
| Opus 5 | $0.00000 | $0.00409 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
p3-arch-techstack 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-arch-techstack – Tech Stack Decision
Selects the tech stack and justifies each technology decision.
Argument: $ARGUMENTS = [Preference, e.g. "Vanilla JS", "React", "Single-File"]
If provided: Consider the preference and check its suitability. If not provided: Recommend based on architecture and project requirements.
Prerequisites
- Component diagram from
/p3-arch-componentsavailable
Agent
- Type: system-architekt
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From ARCHITECTURE.md: Component diagram (overview only)
- From CLAUDE.md: Briefing preference for tech stack
- From VALIDATION.md: PoC tech findings (if available)
Prompt Template
Goal: Select tech stack for the project. Preference: $ARGUMENTS
Architecture: [inline component diagram]
Output Format: Table: | Area | Technology | Justification | Alternatives | Areas: Frontend, Backend, Database, Build Tool, Hosting, External Services
Constraints:
- ONLY tech stack, NO architecture changes
- Justification max. 1 sentence per technology
- Max. 8 rows
Orchestrator Checkpoint
- Every technology has a justification?
- Briefing preference considered or explicitly rejected with reasoning?
Write Detail File
Write the result to docs/architecture/TECH_STACK.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: arch-techstack
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Stack Overview (the table Area / Technology / Justification / Alternatives), ## Open Trade-offs (decisions still to confirm in implementation).
Update Phase Index
Update docs/architecture/ARCHITECTURE.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In Detail Files table: ensure a row for
[TECH_STACK.md](TECH_STACK.md)with statuscomplete. - Lift load-bearing tech-stack decisions into Key Decisions (1 line each, e.g.
- Frontend: SwiftUI → see TECH_STACK.md).
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 · 84 lines · 0 tokens per session scan A 0f1f686edf70
p3-arch-techstack 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 819 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…