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-telemetry-emission-scangit 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-telemetry-emission-scan)<a href="https://agentmods.dev/skills/ollygarden/opentelemetry-agent-skills/otel-telemetry-emission-scan"><img src="https://agentmods.dev/badge/skills/ollygarden/opentelemetry-agent-skills/otel-telemetry-emission-scan/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-telemetry-emission-scan"><img src="https://agentmods.dev/badge/skills/ollygarden/opentelemetry-agent-skills/otel-telemetry-emission-scan.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.00069 | $0.00734 |
| Opus 5 | $0.00034 | $0.00367 |
| Sonnet 5 | $0.00014 | $0.00147 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
otel-component-telemetry 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 12d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You scan one component from the OpenTelemetry ecosystem and write its telemetry emission inventory.
Repo: ${Repo} Path: ${Path} Versions to scan: ${Version} Tag prefix: ${TagPrefix} Force: ${Force} Output root: ${OutDir}
Output
Procedure
-
Resolve versions. The repo is already cloned locally at
/tmp/otel-component-telemetry/<repo basename>— do not clone it yourself. List the component's requested number of released versions from its git tags (git tag). WhenTag prefixis non-empty, consider only tags beginning with that literal prefix, check out the full tag, and strip the prefix to obtain the version used in frontmatter and the output filename. In monorepos where packages version independently of repo tags and no tag prefix is provided (e.g. opentelemetry-js experimental packages), use the package's own version from its manifest at each release tag, and name files after the package version. -
Get source. Check out each resolved tag into its own temp directory:
git worktree add "$(mktemp -d)" <tag>. Never scan a branch — only pinned tags. -
Ground truth in the code. Analyse the instrumentaiton inside a codebase deeply and identify all emitted instrumentation data points required to fill the below table format.
-
Record conditionality. If a signal, metric, or attribute is gated (feature gate, opt-in config, experimental semconv env var), it still gets a row — with the gate named in
Notes. -
Apply the skip/force rule, run the self-check, write the file(s).
Updates
- A version whose file already exists is skipped — existence means scanned.
- If your prompt says
force: true, scan it anyway and reconcile: compare our findings with the existing file and edit only rows that are wrong or missing. Do not rewrite the whole file.
Never modify files of other components.
Output
Output one file per scanned version under the output root given above, mirroring repo + path:
${OutDir}/<repo basename>/<path>/v<version>.md
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.
- 12d ago First seen · 80 lines · 69 tokens per session scan A 37f4840d63e2
otel-component-telemetry is a skill published in the GitHub repository ollygarden/opentelemetry-agent-skills (98 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 734 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.