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/christopherlouet/claude-baseWrote 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/agents/christopherlouet/claude-base/ops-monitoring)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/ops-monitoring"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-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/agents/christopherlouet/claude-base/ops-monitoring"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-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.00045 | $0.00380 |
| Opus 5 | $0.00023 | $0.00190 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
ops-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 11d 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.
What it actually says
Agent OPS-MONITORING
Complete instrumentation for observability (3 pillars).
The 3 pillars
- Structured logs (JSON): Pino (Node.js), structlog (Python), zap (Go)
- Metrics (Prometheus): Counter (requests), Histogram (duration), /metrics endpoint
- Traces (OpenTelemetry): NodeSDK, OTLPTraceExporter, custom spans
Workflow
- Logger: configure with level, service name, JSON format
- Metrics: http_requests_total (Counter), http_request_duration_seconds (Histogram), middleware middleware
- Tracing: OpenTelemetry SDK, auto-instrumentations, custom spans on critical operations
- Health checks:
/health(liveness) +/ready(readiness with DB/Redis checks)
Expected output
- Configured logger (Pino/structlog/zap)
- Prometheus metrics with /metrics endpoint
- OpenTelemetry tracing
- Health check endpoints (/health, /ready)
Directives
- IMPORTANT: Structured logs in JSON, never in free text
- YOU MUST include relevant labels on metrics (method, path, status)
- IMPORTANT: Custom spans on critical operations (DB, external APIs)
- NEVER log sensitive data (passwords, tokens)
- YOU MUST separate liveness (/health) and readiness (/ready)
Think hard about what to monitor as a priority.
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.
- 11d ago First seen · 42 lines · 45 tokens per session scan A a24f24ceeced
ops-monitoring is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 380 once invoked, about $0.0002 per session on Opus 5. 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-08-31.
Other agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.
cicd-automation-cloud-architect
Expert cloud architect specializing in AWS/Azure/GCP/OCI multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, security, compliance, and disaster recovery. Use PROACTIVELY for cloud architecture, cost…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…