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 skills add cyanheads/orcid-mcp-server --skill api-telemetrygit clone --depth 1 https://github.com/cyanheads/orcid-mcp-serverWrote 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/cyanheads/orcid-mcp-server/api-telemetry)<a href="https://agentmods.dev/skills/cyanheads/orcid-mcp-server/api-telemetry"><img src="https://agentmods.dev/badge/skills/cyanheads/orcid-mcp-server/api-telemetry/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/cyanheads/orcid-mcp-server/api-telemetry"><img src="https://agentmods.dev/badge/skills/cyanheads/orcid-mcp-server/api-telemetry.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.00085 | $0.10529 |
| Opus 5.5 | $0.00034 | $0.04212 |
| Sonnet 5.5 | $0.00017 | $0.02106 |
| Haiku 4.5 | $0.00009 | $0.01053 |
Grade A, and why
api-telemetry 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.
This is a copy
100% identical to api-telemetry — 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
The framework auto-instruments every tool, resource, prompt, storage, LLM, speech, and graph call — each gets its own span and the standard counters/histograms. HTTP server requests pick up spans from HttpInstrumentation (all Node.js HTTP traffic, skips /healthz) plus httpInstrumentationMiddleware from @hono/otel on the MCP HTTP endpoint when installed (optional Tier 3 peer — bun add @hono/otel). On Bun, HttpInstrumentation silently no-ops and @hono/otel is the only HTTP coverage. Auth checks and session lifecycle are tracked as metrics only — auth decorates the active HTTP span with attributes, sessions emit counters.
requestId, traceId, and tenantId correlate automatically across spans, metrics, and logs. Framework log records carry traceId/spanId from the request context.
A handler's ctx.traceId / ctx.spanId name the execution span it runs in — tool_execution:<name> or resource_read:<name> — not the enclosing HTTP request span. Under HTTP the trace ID is the request's, so handler logs join to the request; the span ID is the child execution's, so they join to that span's attributes and duration. On stdio, where no transport span exists, both are still populated from the execution span the framework opens. Both are undefined when telemetry is disabled: the non-recording span a disabled pipeline produces carries all-zero IDs, and the framework reports no correlation rather than IDs that correlate to nothing.
For the helper API surface (withSpan, createCounter, createHistogram, buildTraceparent, etc.) — see the api-utils skill, Telemetry section. This skill is the catalog of what is emitted; that one is the reference for how to emit your own.
Enabling export
OTel is off by default. OTEL_ENABLED=true alone does nothing — you also need an OTLP endpoint. Without an endpoint the SDK is configured but nothing leaves the process.
| Env var | Default | Purpose |
|---|---|---|
OTEL_ENABLED |
false |
Master switch. Must be true to start the SDK. |
OTEL_EXPORTER_OTLP_ENDPOINT |
— | OTLP/HTTP base URL (e.g. http://localhost:4318). Traces go to <base>/v1/traces, metrics to <base>/v1/metrics; a path prefix is kept. |
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT |
— | OTLP/HTTP traces endpoint (e.g. http://localhost:4318/v1/traces). Overrides the base for traces; used as-is. |
OTEL_EXPORTER_OTLP_METRICS_ENDPOINT |
— | OTLP/HTTP metrics endpoint (e.g. http://localhost:4318/v1/metrics). Overrides the base for metrics; used as-is. |
OTEL_EXPORTER_OTLP_LOGS_ENDPOINT |
— | OTLP/HTTP logs endpoint (e.g. http://localhost:4318/v1/logs). Opt-in log export; used as-is and never derived from the base. |
OTEL_SERVICE_NAME |
createApp name → package.json name |
service.name resource attribute. Seeded from createApp({ name }) when unset; an env value wins. |
OTEL_SERVICE_VERSION |
package.json version |
service.version resource attribute. |
OTEL_TRACES_SAMPLER_ARG |
1.0 |
Trace sampling ratio (0–1) for TraceIdRatioBasedSampler. |
OTEL_LOG_LEVEL |
INFO |
OTel diagnostic logger level (NONE/ERROR/WARN/INFO/DEBUG/VERBOSE/ALL; warning/err/information accepted). Diag output goes to stderr at every level, never stdout. |
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 Changed · +8 lines 8fd13da56906
- 17d ago Changed · +29 lines e807660354fb
- 28d ago Changed · +39 lines 24aa1e46913c
- 1mo ago Changed · +3 lines 50f43b4c7565
- 1mo ago First seen · 253 lines · 85 tokens per session scan A bb656e39dd17
api-telemetry is a skill published in the GitHub repository cyanheads/orcid-mcp-server (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 85 tokens to every session and 10,529 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to api-telemetry, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.clientCapabilities, ctx.enrich, ctx.content), and when to use each.
add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…
orchestrations
Pick and run a multi-phase workflow that chains foundational task skills (git-wrapup, release-and-publish, maintenance, field-test, setup, etc.) end-to-end. Routes user intent to a workflow file under workflows/ — greenfield builds, maintenance + release, field-test + fix, or known-work + release. Single source for…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…