Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add honeycombio/agent-skill/plugin install honeycombWrote 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/honeycombio/agent-skill/otel-genai-instrumentation)<a href="https://agentmods.dev/skills/honeycombio/agent-skill/otel-genai-instrumentation"><img src="https://agentmods.dev/badge/skills/honeycombio/agent-skill/otel-genai-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/honeycombio/agent-skill/otel-genai-instrumentation"><img src="https://agentmods.dev/badge/skills/honeycombio/agent-skill/otel-genai-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.00146 | $0.07226 |
| Opus 5 | $0.00073 | $0.03613 |
| Sonnet 5 | $0.00029 | $0.01445 |
| Haiku 4.5 | $0.00015 | $0.00723 |
Grade A, and why
otel-genai-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 11d 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 — 666 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GenAI Instrumentation for Honeycomb
Instrumenting LLM and agent applications using OTel Semantic Conventions for GenAI (currently v1.40.0, Development status). For conceptual foundations, see the observability-fundamentals skill.
Base OTEL Setup (Required First)
BEFORE implementing GenAI instrumentation, ensure your base OpenTelemetry configuration is complete.
Use the otel-instrumentation skill to configure all standard OTEL environment variables (OTEL_SERVICE_NAME, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_HEADERS, OTEL_EXPORTER_OTLP_PROTOCOL, signal-specific endpoints, etc.) and verify basic spans are flowing to Honeycomb.
GenAI instrumentation adds GenAI-specific configuration on top of that base setup.
Critical Requirements (Non-Negotiable)
BEFORE implementing any GenAI instrumentation, complete these steps in order:
Step 1: Ask About Content Capture (FIRST!)
Stop and ask the user this question BEFORE writing any code or configuration:
"Do you want to capture the actual prompts and model responses in your traces?
Enabling content capture:
- ✅ Helps debug tool call failures, planning loops, and agent deadlocks
- ✅ Lets you see why the model made specific decisions
- ❌ Captures potentially sensitive content (user prompts, model responses)
- ❌ May contain PII, proprietary data, or confidential information
Recommended for: debugging/development, non-sensitive data, or if you have filtering
Not recommended for: production with sensitive data, PII/health/financial info"
Record their answer — you'll need it when configuring instrumentation.
Step 2: Enable GenAI Conventions (REQUIRED)
export OTEL_SEMCONV_STABILITY_OPT_IN=gen_ai_latest_experimental
Without this, GenAI spans will not be created.
Step 3: Set Required Attributes on EVERY Span (REQUIRED)
gen_ai.operation.name— e.g.,chat,execute_tool,invoke_agentgen_ai.conversation.id— same value for all spans in a conversation
What ships with it
7 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.
- references/agent-and-tool-patterns.md 11 KB
- references/auto-instrumentation-setup.md 4.2 KB
- references/content-capture-setup.md 7.9 KB
- references/genai-attributes-catalog.md 2.1 KB
- references/manual-instrumentation.md 29 KB
- references/mcp-instrumentation.md 5.6 KB
- references/streaming-instrumentation.md 11 KB
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.
- 11d ago First seen · 666 lines · 146 tokens per session scan A 0f7b997b4df4
otel-genai-instrumentation is a skill published in the GitHub repository honeycombio/agent-skill (22 stars, last pushed 15d ago), licensed MIT. It adds 146 tokens to every session and 7,226 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…