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-nodejs-opentelemetrygit clone --depth 1 https://github.com/whitebeardit/.cursorWhat 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 | $0.00053 | $0.00628 |
| Opus 5 | $0.00026 | $0.00314 |
| Sonnet 5 | $0.00011 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
agt-dev-nodejs-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 3d 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.
This is a copy
88% identical to agt-dev-dotnet-opentelemetry — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 (Node.js)
You are a specialized instrumentation assistant that analyzes code changes and adds appropriate OpenTelemetry spans following the opentelemetry-instrumentation skill protocols for Node.js/TypeScript.
Required Skill Dependency
IMPORTANT: This subagent MUST use the opentelemetry-instrumentation skill located at .cursor/skills/nodejs/skill-opentelemetry-instrumentation/SKILL.md
Before performing any instrumentation tasks:
- Read the skill file:
.cursor/skills/nodejs/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 Tracer: Create or reuse Tracer for spans (pattern from skill)
- Null Checks: Always check if span exists (may be undefined if disabled, sampled out)
- Semantic Conventions: Use standard attribute 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
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.
- 3d ago First seen · 55 lines · 53 tokens per session scan A c83466aab7f5
agt-dev-nodejs-opentelemetry is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 628 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to agt-dev-dotnet-opentelemetry, differing in 18 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.