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 instructions/devtheops/opencode-plugin-otel/agents-mdgit clone --depth 1 https://github.com/DEVtheOPS/opencode-plugin-otelWhat 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.00893 | $0.00893 |
| Opus 5 | $0.00447 | $0.00447 |
| Sonnet 5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
opencode-plugin-otel AGENTS.md 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI agents working in this repository.
Build & typecheck
Always run after making changes:
bun run typecheck
There is no build step. TypeScript source files are published directly and loaded natively by Bun.
Testing
bun test
Project layout
src/
├── index.ts — Plugin entrypoint
├── types.ts — Shared types
├── config.ts — Env config and log level
├── otel.ts — OTel SDK setup and instruments
├── probe.ts — OTLP endpoint TCP probe
├── util.ts — errorSummary, setBoundedMap
└── handlers/
├── session.ts — Session lifecycle events
├── message.ts — LLM message and tool part events
├── permission.ts — Tool permission events
└── activity.ts — File diffs and git commits
Key conventions
- Bun over Node — use
bun,bun test,bun run. Never usenode,npx,jest, orvitest. - No comments unless explicitly requested.
- No
sdk-node— the OTel Node SDK meta-package is intentionally excluded; use individual packages. HandlerContext— all event handlers receive aHandlerContext(defined insrc/types.ts). Do not importclientor OTel globals directly inside handlers; thread them through the context.setBoundedMap— always use this instead ofMap.setforpendingToolSpansandpendingPermissionsto prevent unbounded growth.- Single source of truth for tokens/cost — token and cost counters are incremented only in
message.updated(src/handlers/message.ts), never instep-finish. - Shutdown — OTel providers are flushed via
SIGTERM/SIGINT/beforeExit. Do not useprocess.on("exit")for async flushing. - All env vars are
OPENCODE_prefixed —OPENCODE_ENABLE_TELEMETRY,OPENCODE_OTLP_ENDPOINT,OPENCODE_OTLP_METRICS_INTERVAL,OPENCODE_OTLP_LOGS_INTERVAL,OPENCODE_METRIC_PREFIX,OPENCODE_CAPTURE_PROMPT_IN_LOGS,OPENCODE_OTLP_HEADERS,OPENCODE_RESOURCE_ATTRIBUTES,OPENCODE_SPAN_ATTRIBUTES. Never use bareOTEL_*names for plugin config.loadConfigcopiesOPENCODE_OTLP_HEADERS→OTEL_EXPORTER_OTLP_HEADERSandOPENCODE_RESOURCE_ATTRIBUTES→OTEL_RESOURCE_ATTRIBUTESbefore the SDK initializes. OPENCODE_ENABLE_TELEMETRY— all OTel instrumentation is gated on this env var. The plugin always loads regardless; only telemetry is disabled when unset.OPENCODE_METRIC_PREFIX— defaults toopencode.; set toclaude_code.for Claude Code dashboard compatibility.- Plugin options —
loadConfigalso accepts anOtelPluginOptionsobject passed via opencode's plugin tuple form (["opencode-plugin-otel", { ... }], threaded throughOtelPlugin's second argument). Precedence is option →OPENCODE_*env → default. Keep option keys 1:1 withPluginConfigfield names.
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.
- 2d ago First seen · 71 lines · 893 tokens per session scan A c85fe86ae44a
opencode-plugin-otel AGENTS.md is an instructions file published in the GitHub repository DEVtheOPS/opencode-plugin-otel (122 stars, last pushed 23d ago), licensed MPL-2.0. It adds 893 tokens to every session, about $0.0045 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.