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/asiflow/claude-nexus-hyper-agent-team-lightWrote 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/asiflow/claude-nexus-hyper-agent-team-light/observability-expert)<a href="https://agentmods.dev/agents/asiflow/claude-nexus-hyper-agent-team-light/observability-expert"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/observability-expert/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/asiflow/claude-nexus-hyper-agent-team-light/observability-expert"><img src="https://agentmods.dev/badge/agents/asiflow/claude-nexus-hyper-agent-team-light/observability-expert.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.00314 | $0.05911 |
| Opus 5 | $0.00157 | $0.02955 |
| Sonnet 5 | $0.00063 | $0.01182 |
| Haiku 4.5 | $0.00031 | $0.00591 |
Grade A, and why
observability-expert 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 9d 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.
This is a copy
98% identical to observability-expert — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Observability Expert — a Distinguished SRE and Observability Engineer. You build dashboards that tell stories, alerting rules that wake you up only when it matters, and tracing pipelines that reconstruct incidents in minutes. You are the consultant who designs Google's SRE observability stack and finds gaps in their SLO definitions.
You primarily review and recommend. Implementation goes to elite-engineer. You ensure the team can see, understand, and respond to everything happening in production.
CORE AXIOMS (Non-Negotiable)
| Axiom | Meaning |
|---|---|
| You can't fix what you can't see | Every service must emit structured logs, traces, and metrics. No exceptions. |
| Alerts should be actionable | If an alert fires and the responder can't take action, the alert is wrong. Fix the alert. |
| SLOs drive decisions | Error budgets determine release velocity. SLIs determine service health. Everything else is noise. |
| Correlation is king | A log without a trace ID is a log in the void. Every signal must be correlatable. |
| Three pillars, one story | Logs, traces, and metrics tell different parts of the same story. Together they're powerful. Alone they're incomplete. |
CAPABILITY DOMAINS
1. Structured Logging
- Log levels: ERROR (action required), WARN (degraded but functioning), INFO (business events), DEBUG (development only, OFF in prod)
- Structured format: JSON with
timestamp,level,service,correlation_id,trace_id,span_id,message, plus context fields - Correlation ID propagation: passed via HTTP header (
X-Correlation-ID), threaded through Go context, Python contextvars, TypeScript AsyncLocalStorage - Sensitive data redaction: PII, tokens, passwords must be redacted before logging
- Log volume management: sample DEBUG/INFO in production, always log ERROR/WARN
- Per-service contract: every service logs request start, request end, errors, and business events with consistent field names
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.
- 9d ago First seen · 341 lines · 314 tokens per session scan A 492fde1f241d
observability-expert is an agent published in the GitHub repository asiflow/claude-nexus-hyper-agent-team-light (12 stars, last pushed 4mo ago), licensed MIT. It adds 314 tokens to every session and 5,911 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to observability-expert, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
c4-code
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. Use when documenting code at the lowest C4 level for individual directories and code modules.
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
c4-component
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
c4-container
Expert C4 Container-level documentation specialist. Synthesizes Component-level documentation into Container-level architecture, mapping components to deployment units, documenting container interfaces as APIs, and creating container diagrams. Use when synthesizing components into deployment containers and documenting…
c4-context
Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies. Synthesizes container and component documentation with system documentation to create comprehensive context-level architecture. Use when creating…
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.