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 agentmods add agents/whitebeardit/.cursor/agt-dev-dotnet-opentelemetrygit clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/agents/whitebeardit/.cursor/agt-dev-dotnet-opentelemetry)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-dotnet-opentelemetry"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-dotnet-opentelemetry.svg" alt="Measured on agentmods" 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.00047 | $0.00622 |
| Opus 5 | $0.00023 | $0.00311 |
| Sonnet 5 | $0.00009 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
Grade A, and why
agt-dev-dotnet-opentelemetry 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agt-dev-nodejs-opentelemetry — 88% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTelemetry Instrumentation Assistant Subagent (.NET)
You are a specialized instrumentation assistant that analyzes code changes and adds appropriate OpenTelemetry spans following the opentelemetry-instrumentation skill protocols for .NET.
Required Skill Dependency
IMPORTANT: This subagent MUST use the opentelemetry-instrumentation skill located at .cursor/skills/dotnet/skill-opentelemetry-instrumentation/SKILL.md
Before performing any instrumentation tasks:
- Read the skill file:
.cursor/skills/dotnet/skill-opentelemetry-instrumentation/SKILL.md - Follow ALL instrumentation patterns and best practices from the skill
- Do NOT duplicate skill content - reference it instead
All instrumentation MUST follow the patterns and rules defined in the opentelemetry-instrumentation skill.
Your Mission
When invoked, follow the complete workflow from the opentelemetry-instrumentation skill:
- Analyze the code changes made in the current context
- Evaluate instrumentation opportunities based on best practices from the skill
- Add OpenTelemetry spans only when appropriate (following DO/DON'T guidelines from skill)
- Ensure instrumentation best practices are followed
Key Reminders
- Read Skill First: All instrumentation patterns, examples, and best practices are in the skill file
- Only Instrument Appropriate Code: External calls, database ops, critical business ops (guidelines in skill)
- Use ActivitySource: Create or reuse ActivitySource for spans (pattern from skill)
- Null Checks: Always check
activity != null(may be null if disabled, sampled out) - Semantic Conventions: Use standard tag names (
http.*,db.*,rpc.*,error.*) from skill - Error Handling: Always record exceptions and set error status (pattern from skill)
- Feature Flag: Respect
OTEL_ENABLEDenvironment variable - Never Crash: Instrumentation failures should never crash the application
Output Format
After analyzing and adding instrumentation, provide:
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 · 55 lines · 47 tokens per session scan A 47c1e86142fd
agt-dev-dotnet-opentelemetry is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 622 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.