opentelemetry-instrumentation

opentelemetry-instrumentation is a skill for Claude Code, Codex from whitebeardit/.cursor. It costs 61 tokens per session (3,544 once invoked), scanned A, original, MIT.

A set of instructions for adding OpenTelemetry tracing to .NET applications. OpenTelemetry records timed steps, called spans, so requests can be followed through services, databases, and other systems.

In plain words
What is it for?
Use it when tracing HTTP, SOAP, or gRPC calls, database work, business operations, batch jobs, or message-queue integrations in .NET Framework 4.8 or .NET 8 applications.
Why use it?
It helps developers see where a request spends time and where failures occur across application boundaries. It also explains which operations are worth tracing and which simple operations should be left alone.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when tracing HTTP, SOAP, or gRPC calls, database work, business operations, batch jobs, or message-queue integrations in .NET Framework 4.8 or .NET 8 applications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/whitebeardit/.cursor/skill-opentelemetry-instrumentation
Install

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.

Any agent
npx skills add whitebeardit/.cursor --skill skill-opentelemetry-instrumentation
Clone the repo
git clone --depth 1 https://github.com/whitebeardit/.cursor

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for opentelemetry-instrumentation

README.md
[![agentmods](https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-opentelemetry-instrumentation/github.svg)](https://agentmods.dev/skills/whitebeardit/.cursor/skill-opentelemetry-instrumentation)
Your own site
<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-opentelemetry-instrumentation"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-opentelemetry-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.

agentmods 80×15 button for opentelemetry-instrumentation

Your own site · 80×15
<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-opentelemetry-instrumentation"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-opentelemetry-instrumentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.03544
Opus 5.5 $0.00024 $0.01418
Sonnet 5.5 $0.00012 $0.00709
Haiku 4.5 $0.00006 $0.00354

Measured 2mo ago against content hash 3b7402be11ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

opentelemetry-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 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.

skills/dotnet/skill-opentelemetry-instrumentation/SKILL.md · 495 lines

How it starts

The opening of the file, as written. The whole thing — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenTelemetry Instrumentation

This skill guides you through instrumenting .NET applications with OpenTelemetry spans, following best practices for distributed tracing.

When to Instrument

✅ DO Instrument:

  • External service calls (HTTP, SOAP, gRPC)
  • Database operations (queries, transactions)
  • Critical business operations (order processing, payment flows)
  • Long-running operations (file processing, batch jobs)
  • Integration points (third-party APIs, message queues)

❌ DON'T Instrument:

  • Simple property getters/setters
  • In-memory operations (dictionary lookups, list operations)
  • Trivial calculations
  • Operations that complete in <1ms consistently

Core Concepts

Activity and ActivitySource

OpenTelemetry uses Activity and ActivitySource for creating spans:

using System.Diagnostics;

// Create ActivitySource (typically one per component/service)
private static readonly ActivitySource ActivitySource = new ActivitySource("MyService");

// Create a span
using (var activity = ActivitySource.StartActivity("operation.name", ActivityKind.Internal))
{
    if (activity != null)
    {
        activity.SetTag("key", "value");
        // Your code here
        activity.SetStatus(ActivityStatusCode.Ok);
    }
}

Activity Kinds

ActivityKind.Server    // Incoming HTTP request
ActivityKind.Client     // Outgoing HTTP/SOAP call
ActivityKind.Internal  // Internal operation
ActivityKind.Producer  // Message queue producer
ActivityKind.Consumer  // Message queue consumer

Instrumentation Patterns

Pattern 1: HTTP Server (ASP.NET)

ASP.NET Core (.NET 8):

// Middleware automatically creates spans for HTTP requests
// Just configure TracerProvider in Program.cs
builder.Services.AddOpenTelemetry()
    .WithTracing(builder => builder
        .AddAspNetCoreInstrumentation() // Automatic HTTP spans
        .AddSource("MyService")          // Your custom spans
        .AddOtlpExporter());

ASP.NET Framework 4.8:

// Global.asax.cs - Application_BeginRequest
protected void Application_BeginRequest(object sender, EventArgs e)
{
    if (!IsOtelEnabled()) return;
    
    var request = HttpContext.Current.Request;
    var activity = TraceabilityHelper.StartSpan(
        $"HTTP {request.HttpMethod} {request.Path}", 
        ActivityKind.Server);
    
    if (activity != null)
    {
        TraceabilityHelper.SetHttpTags(activity, 
            request.HttpMethod, 
            request.Url.ToString(), 
            null);
        HttpContext.Current.Items["OtelRootActivity"] = activity;
    }
}

// Application_EndRequest
protected void Application_EndRequest(object sender, EventArgs e)
{
    if (HttpContext.Current.Items["OtelRootActivity"] is Activity activity)
    {
        var statusCode = HttpContext.Current.Response.StatusCode;
        TraceabilityHelper.SetHttpTags(activity, null, null, statusCode);
        
        if (statusCode >= 400)
            TraceabilityHelper.SetErrorStatus(activity, $"HTTP {statusCode}");
        else
            TraceabilityHelper.SetSuccessStatus(activity);
        
        activity.Dispose();
    }
}

Read the full file on GitHub · 495 lines

Changes

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.

  1. 2mo ago First seen · 495 lines · 61 tokens per session scan A 3b7402be11ff

Subscribe to this mod's changes

opentelemetry-instrumentation is a skill published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 8mo ago), licensed MIT. It adds 61 tokens to every session and 3,544 once invoked, about $0.0002 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.

Related

opentelemetry-instrumentation compared with skills from other repositories

opentelemetry-instrumentation next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
opentelemetry-instrumentationwhitebeardit/.cursorSkill128mo agoMITA61Claude Code, Codex
mem0-oss-to-platformmem0ai/mem0Skill68k2d agoApache-2.0A217Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skillsSkill3.2kyesterdayMITA78Claude Code
fastapi-router-pymicrosoft/skillsSkill3.2kyesterdayMITA46Claude Code
dev-runtimelangwatch/langwatchSkill5.0kyesterdayApache-2.0A172Claude Code
api-designericrisco/rsc-harnessSkill5032d agoMITA105Claude Code, Codex
migrate-segw-to-raparc-mcp/arc-1Skill252yesterdayMITA106Claude Code