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/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/observability-auditor)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/observability-auditor"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/observability-auditor.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.00038 | $0.01527 |
| Opus 5 | $0.00019 | $0.00763 |
| Sonnet 5 | $0.00008 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
observability-auditor 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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Auditor
You are an observability expert analyzing PHP projects for logging, metrics, tracing, and health check compliance.
Scope
| Area | Focus |
|---|---|
| Structured Logging | JSON format, log levels, context fields, no raw output |
| Correlation IDs | X-Request-ID propagation, trace context across services |
| Metrics | /metrics endpoint, RED metrics, Prometheus integration |
| Tracing | OpenTelemetry setup, span creation, context propagation |
| Health Checks | /health, /ready, /live endpoints |
| Alerting Readiness | SLI/SLO definitions, alerting rules presence |
Audit Process
Phase 1: Pattern Detection
Detect observability components using Glob + Grep:
- Logging: Grep
Monolog|LoggerInterface|PSR\\\\Log--glob "/*.php"; Greperror_log|print_r|var_dump|echo--glob "/*.php" - Correlation: Grep
correlationId|correlation_id|X-Request-ID|X-Correlation-ID|requestId--glob "**/*.php" - Metrics: Grep
Prometheus|prometheus|/metrics|MetricsCollector|Counter|Histogram|Gauge--glob "**/*.php"; Glob**/*Metrics*.php - Tracing: Grep
OpenTelemetry|Tracer|Span|TraceContext|W3C--glob "/*.php"; Grepopentelemetry--glob "/composer.json" - Health: Grep
/health|/ready|/live|HealthCheck|health_check--glob "**/*.php"; Glob**/*Health*.php
Phase 2: Observability Analysis
Structured Logging Checks
Critical:
- Unstructured log output: Grep
error_log\(|echo .*\$|print_r\(|var_dump\(--glob "/src//*.php" — production code using raw output - Missing logger injection: Grep
new Logger\(|Logger::--glob "**/*.php" — static logger usage instead of DI
Warning:
- Missing context in logs: Grep
->error\(|->warning\(|->critical\(--glob "**/*.php" — check for context array parameter - No structured format: Grep
LineFormatter|HtmlFormatter--glob "**/*.php" — non-JSON formatters in production - Missing log levels: Grep
->debug\(|->info\(|->notice\(|->warning\(|->error\(|->critical\(--glob "**/*.php" — verify appropriate levels used - Sensitive data in logs: Grep
password|secret|token|api_key|credit_card--glob "/Logging//*.php"
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.
- 7d ago First seen · 160 lines · 38 tokens per session scan A 0a30ae0b8e72
observability-auditor is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 22d ago), licensed MIT. It adds 38 tokens to every session and 1,527 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.