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 F-U-S-E-E/FuseDevelopmentGroup --skill opentelementry-dotnet-instrumentationgit clone --depth 1 https://github.com/F-U-S-E-E/FuseDevelopmentGroupWrote 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/f-u-s-e-e/fusedevelopmentgroup/opentelementry-dotnet-instrumentation)<a href="https://agentmods.dev/skills/f-u-s-e-e/fusedevelopmentgroup/opentelementry-dotnet-instrumentation"><img src="https://agentmods.dev/badge/skills/f-u-s-e-e/fusedevelopmentgroup/opentelementry-dotnet-instrumentation/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/f-u-s-e-e/fusedevelopmentgroup/opentelementry-dotnet-instrumentation"><img src="https://agentmods.dev/badge/skills/f-u-s-e-e/fusedevelopmentgroup/opentelementry-dotnet-instrumentation.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.03797 |
| Opus 5 | $0.00023 | $0.01899 |
| Sonnet 5 | $0.00009 | $0.00759 |
| Haiku 4.5 | $0.00005 | $0.00380 |
Grade A, and why
OpenTelemetry-NET-Instrumentation 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 6d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 6d ago First seen · 478 lines · 45 tokens per session scan A 82c34723b881
OpenTelemetry-NET-Instrumentation is a skill published in the GitHub repository F-U-S-E-E/FuseDevelopmentGroup (22 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 45 tokens to every session and 3,797 once invoked, about $0.0002 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 skills, from other repositories
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.
observability
Use when instrumenting a service from the inside so an incident can be explained from telemetry alone — wiring OpenTelemetry logs, metrics and traces, standing up a Collector, exporting via OTLP, and defining telemetry-driven alerts. NOT outside-in uptime probes, on-call rotation, or who-gets-paged (that is…
golang-observability-opentelemetry
Instrumenting Go applications with OpenTelemetry for distributed tracing, Prometheus for metrics, and structured logging with slog.
opentelemetry
OpenTelemetry observability patterns: traces, metrics, logs, context propagation, OTLP export, Collector pipelines, and troubleshooting.
opentelemetry-docs
OpenTelemetry — vendor-neutral observability: traces, metrics, logs, OTLP, Collector, SDKs, semantic conventions.
Observability & Monitoring
Structured logging, metrics, distributed tracing, and alerting strategies.