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 skills/cookiemonsterdev/agents-skills/opentelemetry-docsnpx skills add cookieMonsterDev/agents-skills --skill opentelemetry-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWrote 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/skills/cookiemonsterdev/agents-skills/opentelemetry-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/opentelemetry-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/opentelemetry-docs.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 | $0.00080 | $0.01080 |
| Opus 5 | $0.00040 | $0.00540 |
| Sonnet 5 | $0.00016 | $0.00216 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
opentelemetry-docs 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTelemetry questions are easy to answer from stale memory or vendor-specific SDK assumptions. Use this skill to ground answers in the official OpenTelemetry documentation and return the closest authoritative page instead of generic observability advice.
When to Use
Use this skill when the request is about:
- OpenTelemetry concepts, signals, and architecture
- Getting started by role: developer, operator, or architect
- Language APIs and SDKs for traces, metrics, and logs
- Zero-code or auto-instrumentation agents
- The OpenTelemetry Collector: receivers, processors, exporters, and pipelines
- Semantic conventions and instrumentation libraries
- OTLP export, compatibility, and integration with other observability tools
- Blueprints, reference implementations, and deployment guidance
- Security, specifications, and contributing to OpenTelemetry
Do not use this skill for:
- Grafana dashboard design or Loki query syntax when the question is Grafana-specific. Use
grafana-docsinstead. - Raw Prometheus scrape config without OpenTelemetry context unless the user is bridging OTel to Prometheus per OTel docs.
- Vendor product docs (Datadog, New Relic, Honeycomb) unless the question is specifically about OpenTelemetry integration patterns documented on opentelemetry.io.
- Application logging frameworks without telemetry export context unless tied to OpenTelemetry logs.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Concepts and getting started
- Language SDK instrumentation
- Zero-code instrumentation
- Collector configuration and deployment
- Signals: traces, metrics, and logs
- Platforms and environments
- Blueprints and reference architectures
- Compatibility and specifications
- Security and operations
If you need a quick starting point, load references/topic-map.md and jump to the closest starting page. For broader discovery, the live docs index is at https://opentelemetry.io/llms.txt.
2. Search official OpenTelemetry docs first
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 103 lines · 80 tokens per session scan A bb1e1e3c214a
opentelemetry-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 16d ago), licensed MIT. It adds 80 tokens to every session and 1,080 once invoked, about $0.0004 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 skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…