OpenInference is a set of conventions and instrumentation plugins for tracing AI applications with OpenTelemetry. It helps developers record language-model calls, retrieval from vector stores, and external tool use for analysis in compatible observability backends. The catalogue entries support instrumentation and use of these tracing conventions.
Borrowing it
Nothing to install: this file belongs to Arize-ai/openinference. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Arize-ai/openinference/main/.agents/skills/js-docs-sync/SKILL.mdgit clone --depth 1 https://github.com/Arize-ai/openinferenceWrote 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/arize-ai/openinference/js-docs-sync)<a href="https://agentmods.dev/skills/arize-ai/openinference/js-docs-sync"><img src="https://agentmods.dev/badge/skills/arize-ai/openinference/js-docs-sync/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/arize-ai/openinference/js-docs-sync"><img src="https://agentmods.dev/badge/skills/arize-ai/openinference/js-docs-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00135 | $0.01393 |
| Opus 5.5 | $0.00054 | $0.00557 |
| Sonnet 5.5 | $0.00027 | $0.00279 |
| Haiku 4.5 | $0.00014 | $0.00139 |
Grade A, and why
js-docs-sync 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 1mo 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JS Package Docs Sync
Verify and update hand-written docs/ documentation in a JS package so it stays
accurate against the actual source code. These docs ship in the npm package (via
the files field in package.json) for coding agents to read from node_modules.
When This Matters
The docs are the contract between the package and coding agents that consume it. Stale signatures, missing exports, or invalid examples mean agents write broken code. Source code is the single source of truth — docs must reflect it exactly.
Workflow
Step 1: Identify the Package
Determine which JS package to sync. If not clear from context, check which
packages have a docs/ directory:
find js/packages -maxdepth 2 -name docs -type d
If only one package has docs, use it. Otherwise ask the user.
Step 2: Understand the Doc Structure
Read docs/README.md in the target package. It contains:
- A Documentation Guide table mapping each doc file to its topic area
- An All Exports at a Glance section listing every public export
- A Source Code Map showing which source files contain what
This is your roadmap — it tells you what each doc file covers and where to look in the source to verify it.
Step 3: Identify What Changed
If this is triggered by source edits, focus on the changed files:
git diff --name-only HEAD~1 -- js/packages/<package>/src/
Map changed source files to the doc files that cover them (using the Source Code Map in README.md). You only need to re-verify the affected docs.
If this is a full review (user asks to "check all docs"), verify everything.
Step 4: Verify Each Doc File
For each doc file that needs checking, compare it against the source code. Check these things in order:
4a. Export Completeness
Read the barrel files (src/index.ts and any sub-module index.ts files) to get
the full list of public exports. Compare against what's listed in docs/README.md
under "All Exports at a Glance". Flag any export that is:
- In source but missing from docs (new export, needs documenting)
- In docs but not actually exported (removed or renamed, needs removing from docs)
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.
- 1mo ago First seen · 152 lines · 135 tokens per session scan A 59dbf0117bdb
js-docs-sync is a skill published in the GitHub repository Arize-ai/openinference (1,291 stars, last pushed today), licensed Apache-2.0. It adds 135 tokens to every session and 1,393 once invoked, about $0.0005 per session on Opus 5.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
trulens-instrumentation
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
observability-phoenix
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
observability
Use when instrumenting a service from the inside so an incident can be explained from telemetry alone — wiring OpenTelemetry logs, metrics and traces, standing up a Collector, exporting via OTLP, and defining telemetry-driven alerts. NOT outside-in uptime probes, on-call rotation, or who-gets-paged (that is…
huawei-cloud-agentarts-otel-ingestion
OpenTelemetry ingestion skill for Huawei Cloud AgentArts observability platform. Provides OTel telemetry data (trace/metrics/logs) ingestion into AgentArts agent-ops, AI Agent observation with genai semantic conventions, auto-configuration for Java/Python/Node.js/Go applications, and ingestion diagnostics and…