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.
git 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-cicd)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-infra-cicd"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-cicd.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.1 | $0.00000 | $0.00881 |
| Opus 5 | $0.00000 | $0.00441 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
p3-infra-cicd 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-infra-cicd – CI/CD Pipeline
Designs the CI/CD pipeline with stages, branch strategy and rollback concept.
Argument: $ARGUMENTS = [Pipeline tool, e.g. "GitHub Actions", "Gitea Actions", "GitLab CI"]
If provided: Use the tool as the specification. If not provided: Recommend based on hosting and infrastructure.
Prerequisites
- Hosting strategy from
/p3-infra-hostingavailable - TECH_STACK.md exists
Agent
- Type: devops
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From INFRASTRUCTURE.md: Hosting strategy and environments
- From TECH_STACK.md: Build tools and frameworks
- From CLAUDE.md: Infrastructure preferences (Gitea, self-hosted)
Prompt Template
Goal: Design CI/CD pipeline. Tool: $ARGUMENTS
Context: [inline from INFRASTRUCTURE.md, TECH_STACK.md]
Output Format:
- Pipeline tool with justification (1 sentence)
- Stages: numbered list | Stage | Content | Duration (estimated) |
- Branch strategy: trunk-based / gitflow with justification (1 sentence)
- Rollback strategy: method and process (2-3 sentences)
Constraints:
- ONLY CI/CD pipeline, NO hosting, NO monitoring
- Max. 8 pipeline stages
- Rollback strategy must be concrete (not just "we do a rollback")
Orchestrator Checkpoint
- All stages sensible for the tech stack?
- Security scan included in the pipeline?
Write Detail File
Write the result to docs/architecture/CICD.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: infra-cicd
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Pipeline Tool (with justification), ## Stages (numbered table stage / content / duration), ## Branch Strategy, ## Rollback Strategy.
Update Sub-Index
Update docs/architecture/INFRA.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[CICD.md](CICD.md)with statuscomplete. - Lift the pipeline tool + branch strategy 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.
- today Changed 2482eefec4c2
- 3d ago First seen · 88 lines · 0 tokens per session scan A 73310daaae3d
p3-infra-cicd 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 881 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
auto
Starts the MindForge Autonomous Execution Engine for the.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
fix-develop
Autonomous fix loop for failing CI on the repo's default branch.
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
debug
Systematic debugging with automated investigation and 4-phase methodology. Default: inline evidence gathering and diagnosis. --deep: spawns systematic-debugger agent for full autonomous debugging. Use for errors, stack traces, test failures, or unexpected behavior.
ccc-makeover
Auto-apply top X-Ray recommendations to improve project health score.