opik-external-integrations

opik-external-integrations is a skill for Claude Code, Codex from comet-ml/opik. It costs 97 tokens per session (1,212 once invoked), scanned A, original, Apache-2.0.

A guide for building Opik integrations that live outside the main Opik repository, such as a separate package or a change to another project's plugin system. An integration connects Opik's tracing to another tool.

In plain words
What is it for?
Use it when the named integration belongs in a separate opik package or in a third-party project such as a framework or platform repository.
Why use it?
It prevents developers from applying Opik's internal repository rules to an external project, whose structure, dependencies, tests, and documentation may follow different conventions.

Skill for Claude CodeCodex

About the project

Opik is an open-source platform for tracing, evaluating, and monitoring applications that use large language models, retrieval systems, or AI agents. Teams use it to inspect agent activity, manage prompts, run evaluations, and monitor these applications in production.

comet-ml/opik · 21,799 stars · on GitHub · comet.com

Install

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.

agentmods
npx agentmods add skills/comet-ml/opik/opik-external-integrations
Any agent
npx skills add comet-ml/opik --skill opik-external-integrations
Clone the repo
git clone --depth 1 https://github.com/comet-ml/opik

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for opik-external-integrations

README.md
[![agentmods](https://agentmods.dev/badge/skills/comet-ml/opik/opik-external-integrations.svg)](https://agentmods.dev/skills/comet-ml/opik/opik-external-integrations)
Your own site
<a href="https://agentmods.dev/skills/comet-ml/opik/opik-external-integrations"><img src="https://agentmods.dev/badge/skills/comet-ml/opik/opik-external-integrations.svg" alt="Measured on agentmods" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,212 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00097 $0.01212
Opus 5 $0.00048 $0.00606
Sonnet 5 $0.00019 $0.00242
Haiku 4.5 $0.00010 $0.00121

Measured 6d ago against content hash 0293f90ab0fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

opik-external-integrations 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 6d 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.

.agents/skills/opik-external-integrations/SKILL.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Opik External Integrations

This skill builds Opik integrations whose code does not live in this repository. Two shapes:

  • Standalone opik-* package / plugin — its own repo or package that depends on the published Opik SDK. Examples: opik-openclaw, opik-claude-code-plugin.
  • Upstream contribution — Opik support added into a third-party project that already has its own logging/callback/plugin system. Examples: an Opik callback in LiteLLM, an Opik integration in Dify.

Activation gate — read this first. Use this skill only when the target lives in an external repo or external package. If the user wants an integration that ships inside sdks/python/src/opik/integrations/ or sdks/typescript/src/opik/integrations/, this is the wrong skill — use opik-integrations. When in doubt, ask the "where does it live" question (below) and route accordingly.

Two principles that make external work different

  1. Follow the HOST repo's conventions, not this repo's. Structure, dependency management, lint/format, test framework, docs, and the contribution guide are dictated by the target project. Do not impose sdks/ layout, fake_backend, or Fern docs on an external repo. Read its CONTRIBUTING/AGENTS.md and mirror its closest existing integration/plugin.
  2. Consume Opik through its PUBLISHED public API. Use the released opik (Python) / opik (TypeScript) SDK or the REST API — the same surface end users get. Never import this repo's internal modules (opik.decorator.*, rest_api, message-processing internals); they are not available outside this repo and are not a stable contract.

Start with the questionnaire

Collect everything up front, free-form — do not propose a target. See workflow.md Phase 0 for the full list. The essentials: which external repo/package (URL + links), integration shape (standalone package vs. upstream contribution vs. plugin), host language/stack, where the Opik code goes, how the host tests and documents, and how to run it to verify.

Read the full file on GitHub · 49 lines

Files

What ships with it

2 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.

Changes

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.

  1. 6d ago First seen · 49 lines · 97 tokens per session scan A 0293f90ab0fc

Subscribe to this mod's changes

opik-external-integrations is a skill published in the GitHub repository comet-ml/opik (21,799 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 1,212 once invoked, about $0.0005 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.