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 skills add ollygarden/opentelemetry-agent-skills --skill otel-declarative-configgit clone --depth 1 https://github.com/ollygarden/opentelemetry-agent-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/ollygarden/opentelemetry-agent-skills/otel-declarative-config)<a href="https://agentmods.dev/skills/ollygarden/opentelemetry-agent-skills/otel-declarative-config"><img src="https://agentmods.dev/badge/skills/ollygarden/opentelemetry-agent-skills/otel-declarative-config/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/skills/ollygarden/opentelemetry-agent-skills/otel-declarative-config"><img src="https://agentmods.dev/badge/skills/ollygarden/opentelemetry-agent-skills/otel-declarative-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00105 | $0.02267 |
| Opus 5 | $0.00053 | $0.01133 |
| Sonnet 5 | $0.00021 | $0.00453 |
| Haiku 4.5 | $0.00011 | $0.00227 |
Grade A, and why
otel-declarative-config 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 8d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTelemetry Declarative Configuration
Selection gate
Identify the exact runtime, package or agent, and version that will parse the file. If they are
unknown, ask for them. Until then, provide only a clearly labeled non-deployable schematic: do not
choose a file_format literal or claim compatibility.
If that runtime lacks declarative support, stop and route to its programmatic or environment-variable
setup instead of inventing YAML.
Missing runtime identity does not defer safety triage. When supplied configuration may be hostile,
first perform the bounded, non-constructing inspection below and report a sanitized diagnosis; then
request the identity before producing a deployable correction.
Sources of Truth
The schema, file_format strings, fields, and SDK coverage evolve per release. Fetch upstream
sources. Cache evidence by the complete runtime/package/agent/version identity, selected schema
tag, and source revision; invalidate it when any key changes and refetch after a schema-related error.
Select a compatible schema release from runtime evidence; do not default to the latest release for
an older parser.
| Fact | Fetch |
|---|---|
| Schema release discovery and selected-tag validation | gh release list --repo open-telemetry/opentelemetry-configuration --exclude-drafts --json tagName,publishedAt --limit 100, then gh release view <schema-release-tag> --repo open-telemetry/opentelemetry-configuration --json tagName,publishedAt,targetCommitish |
Language Support Status (coverage advisory, not authoritative for file_format) |
WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-configuration/main/language-support-status.md |
| Field-by-field docs for the latest release | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-configuration/<schema-release-tag>/schema-docs.md |
| Compiled JSON Schema (validate generated YAML against this) | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-configuration/<schema-release-tag>/opentelemetry_configuration.json |
| Canonical full example | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-configuration/<schema-release-tag>/examples/otel-sdk-config.yaml |
| Migration template (every option, with comments) | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-configuration/<schema-release-tag>/examples/otel-sdk-migration-config.yaml |
| Schema CHANGELOG (breaking-change history with migration steps) | WebFetch https://raw.githubusercontent.com/open-telemetry/opentelemetry-configuration/<schema-release-tag>/CHANGELOG.md |
What ships with it
6 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.
- 8d ago Changed · +11 lines 6187b4d842a8
- 12d ago First seen · 147 lines · 105 tokens per session scan A 63a5d05a05e6
otel-declarative-config is a skill published in the GitHub repository ollygarden/opentelemetry-agent-skills (98 stars, last pushed yesterday), licensed Apache-2.0. It adds 105 tokens to every session and 2,267 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-08-30.
Other skills, from other repositories
phoenix-observability
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
clawmetry-selfcheck
Read your own agent telemetry from ClawMetry (waste, progress, cost) and act on it before finishing a task. Use when ClawMetry is installed on this machine and you want to check whether you are re-reading files, spinning in loops, or burning budget.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
clawmetry
Real-time observability for OpenClaw agents — local dashboard + optional encrypted cloud sync. Tracks costs, tokens, sessions, tool calls, memory, crons, and system health. Access from anywhere via ClawMetry Cloud.