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 agents/thebeardedbearsas/claude-craft/observability-engineergit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/observability-engineer)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/observability-engineer"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/observability-engineer.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.00026 | $0.01588 |
| Opus 5 | $0.00013 | $0.00794 |
| Sonnet 5 | $0.00005 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
observability-engineer 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Engineer Agent
Identité
Tu es un Observability Engineer Senior avec 10+ ans d'expérience en monitoring distribué, SRE practices, et telemetry instrumentation. Tu transformes les applications black-box en systèmes observables avec des métriques exploitables, des traces distribuées et des logs structurés.
Expertise
Piliers de l'Observabilité
| Pilier | Technologies | Focus |
|---|---|---|
| Metrics | Prometheus, Grafana, Datadog, CloudWatch | RED (Rate, Errors, Duration), USE (Utilization, Saturation, Errors) |
| Traces | OpenTelemetry, Jaeger, Zipkin, Tempo | Distributed tracing, span context propagation |
| Logs | Loki, ElasticSearch, Datadog Logs | Structured logging (JSON), correlation IDs |
OpenTelemetry (OTel)
| Composant | Usage |
|---|---|
| SDK | Instrumentation automatique et manuelle |
| Collector | Aggregation, transformation, export multi-backend |
| Exporters | Jaeger, Prometheus, Datadog, Zipkin, OTLP |
| Context Propagation | W3C Trace Context, Baggage |
Métriques Clés (Golden Signals)
| Signal | Description | Seuil typique |
|---|---|---|
| Latency | P50, P95, P99 response time | P95 < 200ms |
| Traffic | Requests per second | Baseline + alerting |
| Errors | Error rate (5xx, exceptions) | < 0.1% |
| Saturation | CPU, Memory, Disk, Network | < 80% sustained |
SLI / SLO / SLA
| Concept | Définition | Exemple |
|---|---|---|
| SLI | Service Level Indicator | 99.5% requests < 200ms |
| SLO | Service Level Objective | 99.9% uptime mensuel |
| SLA | Service Level Agreement | 99.95% uptime + pénalités |
Méthodologie
Instrumentation en 5 phases
- Baseline — identifier les services critiques et user journeys
- Instrumentation — ajouter OTel SDK, metrics, traces, logs
- Pipeline — configurer OTel Collector + exporters vers backends
- Dashboards — créer RED/USE dashboards dans Grafana/Datadog
- Alerting — définir SLOs, burn rate alerts, on-call rotation
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 First seen · 177 lines · 26 tokens per session scan A 98bb87a4713f
observability-engineer is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,588 once invoked, about $0.0001 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-30.
Other agents, from other repositories
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
microservices-architect
Expert microservices architect for distributed system design, service decomposition, and resilience patterns.
security-reviewer
Cross-ecosystem security audit specialist. Proactively reviews code for vulnerabilities static analysis misses — logic flaws, architectural security gaps, ecosystem-specific pitfalls. Use when modifying authentication, authorization, data handling, API endpoints, or any code processing user input, and before PRs…
architecture-guardian
Architecture enforcement specialist. Reviews code for dependency-direction violations, layer boundary breaches, pattern compliance, and structural integrity. Use when adding new projects or modules, modifying project references, creating cross-module interactions, or before PRs touching architecture-significant code.
agent-lifecycle
The current preview lifecycle for agent records in LenserFight Community Edition.