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-upgradegit 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-upgrade)<a href="https://agentmods.dev/skills/ollygarden/opentelemetry-agent-skills/otel-upgrade"><img src="https://agentmods.dev/badge/skills/ollygarden/opentelemetry-agent-skills/otel-upgrade/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-upgrade"><img src="https://agentmods.dev/badge/skills/ollygarden/opentelemetry-agent-skills/otel-upgrade.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.00061 | $0.00754 |
| Opus 5 | $0.00030 | $0.00377 |
| Sonnet 5 | $0.00012 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
otel-upgrade 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTelemetry Upgrade
Find the highest stable target supported by the available repository evidence and provide concise, case-specific upgrade advice. Unless the user asks for implementation, assess the upgrade without changing project files.
Choose the workflow
| Request or repository evidence | Read |
|---|---|
| Package manifests, lockfiles, APIs, SDKs, instrumentation libraries, exporters, plugins, or dependency constraints | Dependency upgrade |
| Collector binaries, images, charts, Operators, configuration, feature gates, components, OCB manifests, builds, or runtime behavior | Collector upgrade |
| A custom Collector involving independently versioned or third-party modules | Read the Collector workflow first, then the dependency workflow for relevant module constraints. |
Read only the applicable reference. Read both when the upgrade crosses both surfaces.
Shared instructions
- Inspect the repository and runtime evidence before choosing the workflow or assuming the ecosystem.
- Establish the exact current and candidate versions. Record wrappers, distributions, artifacts, and embedded dependencies separately rather than treating one version as proof of another.
- Query authoritative registries and tagged primary upstream sources for current stable releases. Record the lookup date. Treat release candidates, beta/alpha packages, nightly artifacts, and untagged source as prereleases unless that package line intentionally publishes with a prerelease identifier; do not silently replace a project's existing experimental package line with a stable package from a different line. If no stable release meets a stated requirement, assess prereleases separately and label them clearly.
- Distinguish the latest available stable release from the highest validated compatible candidate. Do not call a candidate validated when the relevant checks could not run.
- Preserve the user's working tree by validating in a temporary copy, worktree, or equivalent isolated environment. Start with the latest stable candidate. If it fails, diagnose the cause and test selected lower versions when useful; do not assume compatibility is monotonic.
- Connect upstream changes to this repository's actual usage and available downstream contracts. Treat unavailable consumers, environments, and exact-version coverage as unverified.
- Use applicable specialized skills only when they are available. Otherwise use primary upstream sources and repository evidence, and report any resulting verification gaps.
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.
- 8d ago Changed a46a60f866f2
- 12d ago First seen · 59 lines · 61 tokens per session scan A 7d8f944e242d
otel-upgrade is a skill published in the GitHub repository ollygarden/opentelemetry-agent-skills (98 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 754 once invoked, about $0.0003 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.