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 StefanTheCode/dotnet-ai-toolkit --skill opentelemetry-setupgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWrote 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/stefanthecode/dotnet-ai-toolkit/opentelemetry-setup)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/opentelemetry-setup"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/opentelemetry-setup/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/stefanthecode/dotnet-ai-toolkit/opentelemetry-setup"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/opentelemetry-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 12 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00125 | $0.01708 |
| Opus 5.5 | $0.00050 | $0.00683 |
| Sonnet 5.5 | $0.00025 | $0.00342 |
| Haiku 4.5 | $0.00013 | $0.00171 |
Grade A, and why
opentelemetry-setup 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 2mo 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTelemetry Setup (.NET)
Wire up OpenTelemetry in an ASP.NET Core or .NET worker app — traces, metrics, and logs — exported to the backend the user wants, with sensible production defaults.
Input — point it at your project
Don't ask the user to paste Program.cs — point this at the project and inspect what's already there:
- A project or repo root — find
Program.cs/Startup.csand any existing OTel wiring. - A folder or single file — if they point directly at the startup file.
- A GitHub URL — clone first, then inspect:
git clone --depth 1 <url> /tmp/repo && cd /tmp/repo
Discover the current state yourself before generating, e.g.:
find <target> -name Program.cs -o -name Startup.cs | grep -vi "/obj/\|/bin/"
grep -rn "AddOpenTelemetry\|WithTracing\|WithMetrics\|AddOtlpExporter\|UseSerilog" --include=*.cs <target>
If OTel is already partly set up (e.g. metrics but no tracing), extend it rather than starting over, and call out the specific gap. Read the .csproj to see which instrumentation packages are already referenced.
When this runs
The user wants observability in a .NET app: distributed tracing, metrics, structured logs, correlation across services, or export to a specific backend. Inspect the project first, then establish three things (ask only what you can't infer):
- App type — ASP.NET Core API, worker/background service, or library.
- Backend — OTLP collector (vendor-neutral, default), Jaeger, Prometheus + Grafana/Tempo, Azure Monitor / Application Insights, or "just console for now".
- .NET version — defaults assume .NET 8/9.
Workflow
- Confirm app type, backend, and signals wanted (traces / metrics / logs — default all three).
- Generate the
Program.cswiring + required NuGet packages. - Add resource attributes (service name, version, environment) — non-negotiable for usable telemetry.
- Add the relevant instrumentation libraries (ASP.NET Core, HttpClient, EF Core, runtime).
- Show how to emit a custom span and a custom metric.
- Give the export config for the chosen backend, plus the collector/compose snippet if relevant.
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.
- 2mo ago First seen · 182 lines · 125 tokens per session scan A 1cd60ba767ce
opentelemetry-setup is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (26 stars, last pushed 2mo ago), licensed MIT. It adds 125 tokens to every session and 1,708 once invoked, about $0.0005 per session on Opus 5.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.
opentelemetry-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| opentelemetry-setupStefanTheCode/dotnet-ai-toolkit | Skill | 26 | 2mo ago | MIT | A | 125 | Claude Code |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 68k | 2d ago | Apache-2.0 | A | 217 | Claude Code, Codex |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 78 | Claude Code |
| fastapi-router-pymicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 46 | Claude Code |
| dev-runtimelangwatch/langwatch | Skill | 5.0k | yesterday | Apache-2.0 | A | 172 | Claude Code |
| api-designericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | A | 105 | Claude Code, Codex |
| migrate-segw-to-raparc-mcp/arc-1 | Skill | 252 | yesterday | MIT | A | 106 | Claude Code |