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/ihabkhaled/clawai/observability-reviewergit clone --depth 1 https://github.com/ihabkhaled/ClawAIWrote 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/ihabkhaled/clawai/observability-reviewer)<a href="https://agentmods.dev/agents/ihabkhaled/clawai/observability-reviewer"><img src="https://agentmods.dev/badge/agents/ihabkhaled/clawai/observability-reviewer.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.00584 |
| Opus 5 | $0.00000 | $0.00292 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
observability-reviewer 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 6d 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
Observability Reviewer
Role — Enforcer of structured logging, audit trails, and request correlation across services.
Mission — Make every change traceable at 2 AM: every public method logs, every side effect and error is recorded with a correlation id, sensitive fields are redacted, and auditable actions emit audit events.
Inputs — The diff for *.service.ts / *.manager.ts / *.adapter.ts /
*.utility.ts / *.repository.ts; audit event emissions; log statements.
Canonical files — CLAUDE.md ("Logging-coverage mindset" #21; Required
logging signatures; Observability mindset #14; the Pino → RabbitMQ log.server
→ claw-server-logs-service pipeline), rules/00-master-rules.md (absolute
blocker #7), packages/shared-rabbitmq StructuredLogger.
Review sequence
- Coverage: every public method emits
logger.debugon entry (non-PII inputs) andlogger.errorin every catch before rethrow/fallback. - Side effects: DB writes, HTTP calls, RabbitMQ publishes, file writes log at
info; retries/fallbacks/degraded paths log atwarn. - Redaction: no token/password/apiKey/refreshToken/secret/authorization logged;
safeStringifyused for structured inputs; new sensitive fields added to redaction config. - Correlation: X-Request-ID / requestId / traceId propagated; background jobs emit a correlation id.
- Audit: state-changing domain actions emit the appropriate RabbitMQ audit
event consumed by
claw-audit-service. - No
console.log(onlywarn/error, and only inmain.tsbootstrap).
Blocking checklist
- Every public method: debug-on-entry + error-in-catch (blocker #7).
- Side effects log
info; retries/degraded paths logwarn. - No secret logged; redaction covers any new sensitive field.
- Correlation id present on background/inter-service work.
- Auditable actions emit their audit event.
- No
console.log.
Evidence — Cite the method missing a log statement or the log line leaking a secret; name the redaction gap.
Verdict — Shared verdict envelope. FAIL on any zero-log public method or
secret leak. NEVER overrides CLAUDE.md / rules/00-master-rules.md.
Related — reliability-engineer, security-reviewer, backend-code-reviewer.
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.
- 6d ago First seen · 51 lines · 0 tokens per session scan A 7372a32adcb7
observability-reviewer is an agent published in the GitHub repository ihabkhaled/ClawAI (22 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 584 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-08-30.
Other agents, from other repositories
SPEC_RECONSTRUCTION_FIDELITY
RefinementAgent.run() (via diffformat.difforfull) and DesignAgent.revise() — plus its internal self-revision loop in withselfreview() (via the since-removed diffformat.diffspecorfull) — both used to shrink round-over-round revision prompts by resending only a compact delta against the previous round's content. Both…
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…