An audit guide for existing OpenTelemetry instrumentation in a Python deployment. OpenTelemetry is a standard way to record traces, metrics, and logs so software behavior can be observed, including when it runs in AWS.

Use it to check tracing setup, exporters, request context, sampling, asynchronous code, span attributes, and AWS X-Ray or ADOT configuration.

It helps find configuration and instrumentation problems that can make requests hard to follow or produce incomplete, misleading, or excessive telemetry.

otel-audit — Command for Claude Code by acaprino

Install

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.

Clone the repo

git clone --depth 1 https://github.com/acaprino/daodan

Made for: Claude Code.

Or install opentelemetry, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/acaprino/daodan/otel-audit/github.svg)](https://agentmods.dev/commands/acaprino/daodan/otel-audit)

Your own site

<a href="https://agentmods.dev/commands/acaprino/daodan/otel-audit"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/otel-audit/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/acaprino/daodan/otel-audit"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/otel-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 98 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,380 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00098	$0.01380
Opus 5	$0.00049	$0.00690
Sonnet 5	$0.00020	$0.00276
Haiku 4.5	$0.00010	$0.00138

Measured 3d ago against content hash 723ad7747178, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

otel-audit 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 3d 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.

exports/claude/plugins/opentelemetry/commands/otel-audit.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenTelemetry Audit

Analyze an existing OpenTelemetry Python instrumentation and produce an actionable audit report.

Instructions

Identify OTel components in the codebase:
- SDK setup (TracerProvider, MeterProvider, LoggerProvider)
- Exporters (OTLP gRPC/HTTP, X-Ray, console)
- Propagators (W3C TraceContext, B3, X-Amzn-Trace-Id, custom)
- Instrumentations (auto-instrumentations, manual spans)
- Samplers (parent-based, trace-id-ratio, always-on)
- Resource detectors (service.name, service.version, aws.ec2, k8s.pod)
- Collector / ADOT config (if present)
Audit each dimension against best practices:

SDK Setup

TracerProvider created once at process start, not per request
service.name and service.version resources set (required for most backends)
Resource detectors attached (aws-ec2 / k8s / ecs / container detectors for cloud)
Shutdown registered (atexit or signal handler) to flush spans on exit

Span Hygiene

Spans use start_as_current_span (context manager) not raw start_span where possible
Status set to ERROR only for infrastructure errors; business-logic rejections leave status UNSET
record_exception used for infrastructure errors, NOT for expected business errors
add_event used for business-logic events instead of new spans
Status is never explicitly set to OK on inner spans (leave UNSET; only the outer request handler may set OK)
Span names are low-cardinality (no IDs or user data in the name)
Attributes use semantic conventions (http.request.method, not httpMethod)

Attribute Budgets

No PII in span attributes or baggage (baggage propagates to ALL downstream services)
No None values in attributes
String attributes truncated if potentially long (> 1KB)
Span attribute count under the per-span limit (default 128)

Context Propagation

Single Propagator chosen intentionally (W3C default, or CompositePropagator for multi-format)
Custom transports (AMQP, ZMQ, Kafka, gRPC without auto-instrumentation) inject/extract correctly
Propagator instances are module-level or cached (not allocated per call)
Async context propagation tested (asyncio, Celery, threading boundaries)

Read the full file on GitHub · 104 lines

Changes

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.

3d ago First seen · 104 lines · 98 tokens per session scan A 723ad7747178

Subscribe to this mod's changes

otel-audit is a command published in the GitHub repository acaprino/daodan (8 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 1,380 once invoked, about $0.0005 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-09-05.

Analytics and metrics Cloud DevOps and cloud

cost-optimize

You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…

wshobson/agents · 0 tokens

deploy

Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.

butterbase-ai/butterbase-skills · 20 tokens

integrate

Set up third-party service integrations.

nxtg-ai/forge-plugin · 6 tokens

env

Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.

vercel/vercel-plugin · 35 tokens

scan

Scan AWS account for cost optimization.

prajapatimehul/claude-aws-cost-saver · 6 tokens

finops-feedback

Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.

glassity/agent-skills · 57 tokens