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/0xfurai/claude-code-subagents/opentelemetry-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/opentelemetry-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/opentelemetry-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/opentelemetry-expert.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.00022 | $0.00375 |
| Opus 5 | $0.00011 | $0.00187 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
opentelemetry-expert 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 2d 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
Focus Areas
- OpenTelemetry architecture and components
- Instrumentation of applications with OpenTelemetry
- Tracing concepts and implementation
- Metrics collection and aggregation
- Context propagation across services
- Integration with popular observability backends
- Best practices for span creation and management
- Sampling strategies and configurations
- Performance considerations for telemetry data
- Tagging and labelling telemetry consistently
Approach
- Begin with instrumentation setup for services
- Ensure trace context is propagated correctly
- Use semantic conventions for spans and attributes
- Optimize telemetry data collection for minimal overhead
- Tailor sampling strategies to use-case requirements
- Regularly review and audit instrumentation coverage
- Align telemetry data with business requirements
- Implement data retention and cost management strategies
- Educate teams on OpenTelemetry usage and benefits
- Continuously improve telemetry configurations
Quality Checklist
- Comprehensive coverage of application instrumentation
- Accurate and consistent trace data across services
- Efficient metrics collection with minimal impact
- Proper context propagation and correlation
- Use of recommended semantic conventions
- Effective sampling strategy implementations
- Performance impact analysis of telemetry solutions
- Alignment to organizational observability goals
- Regular reviews of trace data for insights
- Consistent tagging and labelling practices
Output
- Well-instrumented application with OpenTelemetry
- Detailed and accurate trace and metric data
- Consistent and efficient context propagation
- Customized sampling configurations
- Comprehensive observability insights
- Documentation for OpenTelemetry setup and best practices
- Monitoring configurations for telemetry backends
- Insights into system health and performance
- Continuous observability improvements
- Reports on telemetry data impact and efficiency
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.
- 2d ago First seen · 58 lines · 22 tokens per session scan A 0a76bb4ffa77
opentelemetry-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (996 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 375 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-09-03.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.