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-infra-hostinggit 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-infra-hosting)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-infra-hosting"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-hosting.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.00912 |
| Opus 5 | $0.00000 | $0.00456 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
p3-infra-hosting 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-infra-hosting – Hosting & Deployment Strategy
Plans hosting platform, deployment model, environments and CDN strategy.
Argument: $ARGUMENTS = [Platform, e.g. "Hetzner", "Vercel", "local"]
If provided: Use the platform as a starting point. If not provided: Recommend based on architecture and project frame.
Prerequisites
- ARCHITECTURE.md and TECH_STACK.md exist
Agent
- Type: devops
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From ARCHITECTURE.md: Components that need to be deployed
- From TECH_STACK.md: Technologies in use
- From CLAUDE.md: Hosting preference (Hetzner, self-hosted)
- From SECURITY.md: Infrastructure-relevant security requirements
Prompt Template
Goal: Plan hosting and deployment strategy. Platform: $ARGUMENTS
Context: [inline from ARCHITECTURE.md, TECH_STACK.md, CLAUDE.md]
Output Format:
- Hosting platform with justification (1-2 sentences)
- Deployment model: Container / PaaS / VPS / Static
- Environments: Table | Environment | Purpose | URL Schema |
- CDN/Static assets: strategy (1-2 sentences)
- Database hosting: managed vs. self-hosted with justification
Constraints:
- ONLY hosting and deployment, NO CI/CD pipeline, NO monitoring
- Consider hosting preference from CLAUDE.md
- Max. 4 environments
Orchestrator Checkpoint
- Hosting preference considered or rejected with justification?
- Deployment model matches the tech stack?
Write Detail File
Write the result to docs/architecture/HOSTING.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: infra-hosting
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Hosting Platform (with justification), ## Deployment Model, ## Environments (the table environment / purpose / URL schema), ## CDN / Static Assets, ## Database Hosting.
Update Sub-Index
Update docs/architecture/INFRA.md (the infrastructure sub-index, created by /p3-infra if missing):
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[HOSTING.md](HOSTING.md)with statuscomplete. - Lift the hosting platform decision into Key Decisions 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 · 89 lines · 0 tokens per session scan A 75a4853d01a5
p3-infra-hosting 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 912 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
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
mindforge:cdn
Optimize CDN caching and invalidation strategy. Usage: /mindforge:cdn [service] [--target-hit-ratio 95%] [--multi-cdn] [--shield].
mindforge:edge
Design edge computing architecture. Usage: /mindforge:edge [service] [--runtime workers|vercel|deno] [--regions global|specific].
finops
Estimate and optimize cloud infrastructure costs. Usage - /mindforge:finops [service] [--forecast 6m] [--target-savings 20%].
deploy
Execute staged deployment rollout with canary and rollback. Usage - /mindforge:deploy [--depth quick|standard|deep] [--skip-canary] [--rollback].
mindforge:environments
Design environment management system. Usage: /mindforge:environments [scope] [--type preview|ephemeral|staging] [--lifecycle hours|days|permanent].