agentmods.dev

p3-infra-hosting

p3-infra-hosting is a command for Claude Code from jonase47/ccpr. It costs 0 tokens per session (911 once invoked), scanned A, original, MIT.

A plan for where an application runs, how it is deployed, which environments it uses, and how static files are delivered.

In plain words
What is it for?
Use it to choose or evaluate a platform, deployment approach, environments, CDN strategy, and database hosting.
Why use it?
It turns the system architecture into a concrete hosting setup and deployment model.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

not rated 1repo changed 2mo ago A scan 0 tokens original MIT

Good fit Use it to choose or evaluate a platform, deployment approach, environments, CDN strategy, and database hosting.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jonase47/ccpr/p3-infra-hosting
View source ↗ jonase47/ccpr
Install

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.

Clone the repo
git clone --depth 1 https://github.com/jonase47/ccpr

Made for: Claude Code.

Wrote 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.

agentmods badge for p3-infra-hosting

README.md
[![agentmods](https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-hosting/github.svg)](https://agentmods.dev/commands/jonase47/ccpr/p3-infra-hosting)
Your own site
<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-infra-hosting"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-hosting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for p3-infra-hosting

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 911 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00911
Opus 5.5 $0.00000 $0.00364
Sonnet 5.5 $0.00000 $0.00182
Haiku 4.5 $0.00000 $0.00091

Measured 2mo ago against content hash c0cc5c02a066, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

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.

commands/p3-infra-hosting.md · 89 lines

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:

  1. Hosting platform with justification (1-2 sentences)
  2. Deployment model: Container / PaaS / VPS / Static
  3. Environments: Table | Environment | Purpose | URL Schema |
  4. CDN/Static assets: strategy (1-2 sentences)
  5. 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 status complete.
  • Lift the hosting platform decision into Key Decisions of the sub-index.
  • Do not edit ARCHITECTURE.md directly.

Read the full file on GitHub · 89 lines

Changes

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.

  1. 2mo ago Changed c0cc5c02a066
  2. 2mo ago First seen · 89 lines · 0 tokens per session scan A 75a4853d01a5

Subscribe to this mod's changes

p3-infra-hosting is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 911 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.

Claude CodeCloudDevOps and cloudagentic-workflowsai-agentsanthropicclaudeclaude-code-agents
Related

p3-infra-hosting compared with commands from other repositories

p3-infra-hosting next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
p3-infra-hostingjonase47/ccprCommand11mo agoMITA0Claude Code
firebase-publishPierry/harness-kitCommand41mo agoMITA20Claude Code
statsAR6420/Hail_HydraCommand517d agoMITA29Claude Code
debugjoaquimscosta/arkhe-claude-pluginsCommand2223d agoMITA48Claude Code
forge-compact-taskluiseiman/dotforgeCommand83d agoMITA46Claude Code
forge-resetluiseiman/dotforgeCommand83d agoMITA15Claude Code
_conventionsbuild-with-dhiraj/ai-workflow-framework-portability-kitCommand51mo agoMITA0Claude Code