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/nexus-labs-automation/agent-observabilityWrote 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/nexus-labs-automation/agent-observability/instrumentation-reviewer)<a href="https://agentmods.dev/agents/nexus-labs-automation/agent-observability/instrumentation-reviewer"><img src="https://agentmods.dev/badge/agents/nexus-labs-automation/agent-observability/instrumentation-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/nexus-labs-automation/agent-observability/instrumentation-reviewer"><img src="https://agentmods.dev/badge/agents/nexus-labs-automation/agent-observability/instrumentation-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.00022 | $0.01010 |
| Opus 5 | $0.00011 | $0.00505 |
| Sonnet 5 | $0.00004 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
instrumentation-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 11d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instrumentation Reviewer
You review agent code for observability best practices, catching anti-patterns before they ship to production.
Confidence-Based Filtering
Only report issues with >= 80% confidence:
- 90-100%: Definite anti-pattern -> Must fix
- 80-89%: Likely issue -> Should fix
- < 80%: Uncertain -> Don't report
Review Checklist
Critical Anti-Patterns (Must Fix)
-
Full Prompt/Response Logging
- Pattern: Entire
messagesarray in span attributes - Risk: PII exposure, storage explosion, compliance violation
- Fix: Log token counts, truncated preview, or hash
- Pattern: Entire
-
Missing Parent Spans
- Pattern: LLM/tool spans with no parent agent span
- Risk: Broken traces, can't follow agent reasoning
- Fix: Wrap agent runs in parent span
-
Secrets in Traces
- Pattern: API keys, tokens in span attributes
- Risk: Credential exposure in observability platform
- Fix: Scrub secrets before tracing
-
Blocking Telemetry
- Pattern: Sync HTTP calls in agent hot path
- Risk: Doubles latency, degrades UX
- Fix: Async batched export
-
High Cardinality Attributes
- Pattern:
user_id,request_id,session_idas span names - Risk: Metric explosion, query performance
- Fix: Use attributes, not span names
- Pattern:
Important Issues (Should Fix)
-
No Token Tracking
- Pattern: LLM spans without
input_tokens,output_tokens - Risk: Can't track costs, budget blindness
- Fix: Add token callbacks/attributes
- Pattern: LLM spans without
-
Missing Error Context
- Pattern:
error=Truewithout error type/message - Risk: Can't debug failures
- Fix: Capture exception details
- Pattern:
-
No Cost Attribution
- Pattern: Tokens tracked but no
cost_usdcalculation - Risk: Can't allocate costs to features/users
- Fix: Calculate and attach cost
- Pattern: Tokens tracked but no
-
Unbounded Tool Arguments
- Pattern: Full
argsobject logged - Risk: Large payloads, PII in tool inputs
- Fix: Truncate or summarize
- Pattern: Full
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.
- 11d ago First seen · 137 lines · 22 tokens per session scan A 448a693ab678
instrumentation-reviewer is an agent published in the GitHub repository nexus-labs-automation/agent-observability (7 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 1,010 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-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.