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 comet-ml/opik-claude-code-plugin --skill opik-instrumentgit clone --depth 1 https://github.com/comet-ml/opik-claude-code-pluginWrote 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/comet-ml/opik-claude-code-plugin/opik-instrument)<a href="https://agentmods.dev/skills/comet-ml/opik-claude-code-plugin/opik-instrument"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-claude-code-plugin/opik-instrument/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/comet-ml/opik-claude-code-plugin/opik-instrument"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-claude-code-plugin/opik-instrument.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.00101 | $0.02700 |
| Opus 5.5 | $0.00040 | $0.01080 |
| Sonnet 5.5 | $0.00020 | $0.00540 |
| Haiku 4.5 | $0.00010 | $0.00270 |
Grade A, and why
opik-instrument 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.
This is a copy
100% identical to opik-instrument — 40 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instrument — Add Opik Tracing and Verify a Real Trace
Definition of done: a representative, safely-executed path produces a trace that is confirmed in Opik and a direct trace link is returned. If verification can't be completed safely or autonomously, stop at the first genuine blocker and return exactly one concrete next step. Code edits alone are not success.
Operate: opinionated in execution, conservative in code changes, automatic in routine decisions, uncompromising about verifying value — but never by running something unsafe.
Inputs
The entry point is just /opik-instrument (optionally /opik-instrument <path>). Infer everything else; treat these only as optional overrides the user may pass, never as required setup:
- target path (default: project root) · project name (default: inferred from the repo) · run command (default: an inferred safe path) ·
migrate_prompts(default: false).
Never turn inference into a questionnaire. Ask only when you hit a genuine, non-inferable blocker (see Blockers).
Activation — the only in-scope work
1. Configure Opik (one source of truth)
- If
~/.opik.configexists orOPIK_API_KEYis set, use it as-is. - Otherwise run the official flow:
opik configure(Python) /npx opik-ts configure(TypeScript). - Verify the config before instrumenting: run
opik healthcheck— it validates the config, the install, and backend/workspace reachability. If it fails, stop at that Blocker and fix config or connectivity before adding any tracing. - Only add project-local
.envvars if the project already uses that pattern. Never introduce a second config mechanism; never copy secret values between mechanisms.
2. Detect language & framework
Python (*.py, pyproject.toml) or TypeScript (*.ts, package.json). Identify the LLM framework from imports and pick its integration:
| Import | Integration |
|---|---|
openai / anthropic |
track_openai / track_anthropic |
langchain / langgraph |
OpikTracer callback |
crewai / dspy / google-genai / bedrock / llama_index / litellm |
track_crewai / OpikCallback / track_genai / track_bedrock / LlamaIndexCallbackHandler / OpikLogger |
TS: opik-openai / opik-vercel / opik-langchain |
trackOpenAI / OpikExporter / OpikCallbackHandler |
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 · 136 lines · 101 tokens per session scan A 37448b1870dd
opik-instrument is a skill published in the GitHub repository comet-ml/opik-claude-code-plugin (24 stars, last pushed 5d ago), licensed Apache-2.0. It adds 101 tokens to every session and 2,700 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to opik-instrument, differing in 40 lines, and is treated as a copy.
Other skills, from other repositories
claude-bridge
Use when orchestrating multiple Claude Code chats, reading other chats' history, sending messages between chats, or searching across chat sessions. Triggers on phrases like "peer chat", "sister chat", "other chat", "cross-chat", "what is the other agent doing", "find in chats", "manager agent", "worker agent"…
claude-bridge-role-manager
Playbook for a Claude Code agent in the role of orchestrator of 2-N worker peers over the claude-bridge MCP. Use when you have a team of peers and want to efficiently dispatch tasks, gate outputs, resolve conflicts, protect invariants, route memory, and hold the interface to the human owner. Triggers — "I'm the…
claude-bridge-role-memory-keeper
Playbook for a Claude Code agent in the dedicated memory keeper role — single-writer for shared agent memory across a team of 3+ peers. Use when you are designated as the keeper (= other peers send you write candidates, you write them and watch for drift). Memory hygiene + reconciliation against the canon + drift…
claude-bridge-setup
Guide the user through activating claude-bridge live-data hooks in /.claude/settings.json. Use when the user asks how to install the plugin's statusLine wrapper or PostToolUse refresh-limits hook, or when peercontextstatus / ratelimitstatus returns hasLiveData: false with a setupPointer. Triggers — "setup live data"…
video-perception
Use when the user mentions a video file (.mp4, .mov, .avi, .mkv, .webm), a YouTube URL, asks to watch/analyze/review a video, or references video content in conversation.
sanity-singletons
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton…