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-monitoring)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-infra-monitoring"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-monitoring/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.
<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-infra-monitoring"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-monitoring.svg" alt="Reviewed on agentmods" width="80" 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.00867 |
| Opus 5 | $0.00000 | $0.00434 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
p3-infra-monitoring 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 5d 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.
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-monitoring – Monitoring & Observability
Defines logging, metrics, alerting and error tracking.
Argument: $ARGUMENTS = [Focus, e.g. "Alerting", "Logging", "APM"]
If provided: Deep-dive the named area. If not provided: Create complete monitoring concept.
Prerequisites
- INFRASTRUCTURE.md with hosting and CI/CD exists
Agent
- Type: devops
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From INFRASTRUCTURE.md: Hosting platform and deployment model
- From ARCHITECTURE.md: Critical components
- From TECH_STACK.md: Technologies in use
Prompt Template
Goal: Define monitoring and observability. Focus: $ARGUMENTS
Context: [inline from INFRASTRUCTURE.md, ARCHITECTURE.md]
Output Format:
- Logging: tool, retention, log level strategy (2-3 sentences)
- Metrics: Table | Metric | Threshold | Alert |
- Alerting: channels and escalation levels (1-2 sentences)
- Error tracking: tool and integration (1 sentence)
- Uptime monitoring: tool and check interval (1 sentence)
Constraints:
- ONLY monitoring, NO hosting, NO CI/CD
- Max. 8 metrics
- Tools must match the hosting (self-hosted vs. SaaS)
Orchestrator Checkpoint
- Metrics cover CPU, memory, response time, error rate?
- Alerting channels defined?
Write Detail File
Write the result to docs/architecture/MONITORING.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: infra-monitoring
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Logging, ## Metrics (the table metric / threshold / alert), ## Alerting, ## Error Tracking, ## Uptime Monitoring.
Update Sub-Index
Update docs/architecture/INFRA.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[MONITORING.md](MONITORING.md)with statuscomplete. - Lift the headline tool decisions 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.
- 5d ago Changed 6310947e62e9
- 9d ago First seen · 88 lines · 0 tokens per session scan A b9948c6923fe
p3-infra-monitoring is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 867 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
map
View, rebuild, or query the codebase dependency map.
design-intent
Guided UI/visual development with structured exploration, architecture design, and quality review.
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.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery.
forge-compact-task
Compact context with dotforge-standardized hint that preserves decisions, files modified, pending TODOs, behaviors disabled, and last commit. Use at 80% context window instead of waiting for auto-compact.