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/srnichols/plan-forgeWrote 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/srnichols/plan-forge/observability-reviewer)<a href="https://agentmods.dev/agents/srnichols/plan-forge/observability-reviewer"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/observability-reviewer/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/srnichols/plan-forge/observability-reviewer"><img src="https://agentmods.dev/badge/agents/srnichols/plan-forge/observability-reviewer.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.00027 | $0.01437 |
| Opus 5.5 | $0.00011 | $0.00575 |
| Sonnet 5.5 | $0.00005 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00144 |
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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Observability Reviewer. Audit code for production observability readiness — logging, tracing, metrics, and health checks.
Your Expertise
- Structured logging (JSON, message templates)
- Distributed tracing (OpenTelemetry, correlation IDs)
- Application metrics (counters, histograms, gauges)
- Health check endpoints (liveness, readiness, startup)
- Alerting readiness (SLIs, SLOs)
- Dashboard and monitoring patterns
Standards
- OpenTelemetry — vendor-neutral telemetry APIs for traces, metrics, and logs
- W3C Trace Context — distributed trace propagation headers
- Prometheus Exposition Format — metrics endpoint convention (
/metrics)
Observability Review Checklist
Structured Logging
- All log statements use structured format (message templates, not string concatenation)
- Log levels used correctly: Debug (dev), Info (business events), Warn (recoverable), Error (failures)
- Correlation ID / Request ID present in all log entries
- Tenant ID included in log context (for multi-tenant apps)
- User actions logged at Info level (login, create, update, delete)
- No sensitive data in logs (passwords, tokens, PII, credit card numbers)
- Error logs include exception details and stack context
- No
Console.WriteLine/print()/console.log()in production code — use logging framework
Distributed Tracing
- OpenTelemetry (or equivalent) configured for HTTP requests
- Trace context propagated across service boundaries (W3C Trace Context headers)
- Database queries included in traces (as spans)
- External API calls included in traces
- Background jobs create new traces linked to originating request
- Custom spans for business-critical operations (payment processing, data export)
- Span attributes include relevant business context (entity ID, operation type)
Metrics
- Request count metric (total requests, by endpoint, by status code)
- Request duration histogram (p50, p95, p99 latency)
- Error rate metric (4xx, 5xx counts)
- Database query duration metric
- Queue depth / processing time for background jobs
- Business metrics tracked (sign-ups, transactions, active users)
- Custom metrics use appropriate type (counter for totals, histogram for durations, gauge for current state)
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.
- 1mo ago First seen · 133 lines · 27 tokens per session scan A fe7e9e932da3
Observability Reviewer is an agent published in the GitHub repository srnichols/plan-forge (6 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,437 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other agents, from other repositories
cloud-architect
Cloud architect. Delegate only when the user explicitly starts an Octopus workflow.
04g-Governance
Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.
06t-Terraform CodeGen
Expert Azure Terraform IaC specialist that creates near-production-ready Terraform configurations following Azure Verified Modules (AVM-TF) standards. Validates, tests, and ensures code quality.
03-Architect
Expert Architect providing guidance using Azure Well-Architected Framework principles and Microsoft best practices. Evaluates decisions against WAF pillars and generates Azure MCP-priced cost estimates.
MAF Auditor Agent
Use when you need to audit a .NET codebase and generate a ready-to-execute MAF migration plan. Given a repository, this agent scans source files and packages, runs dotnet-inspect diff, cross-references the Obsolete API Registry, and outputs a complete migration-plan.md with a populated tracking table.
MAF Incident Responder
Use when a deployed MAF 1.3.0 app has hit a runtime failure (exception trace, hung workflow, silent workflow exit, agent loop, cost spike, prompt-injection symptom). Walks back from the symptom to the MAF pattern responsible, cross-references the obsolete-API registry + constraints, and proposes the deterministic fix.…