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-mcp --skill opik-instrumentgit clone --depth 1 https://github.com/comet-ml/opik-mcpWrote 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-mcp/opik-instrument)<a href="https://agentmods.dev/skills/comet-ml/opik-mcp/opik-instrument"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-mcp/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-mcp/opik-instrument"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-mcp/opik-instrument.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 8 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium MCP Rug Pull · line 36 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.02630 |
| Opus 5.5 | $0.00040 | $0.01052 |
| Sonnet 5.5 | $0.00020 | $0.00526 |
| Haiku 4.5 | $0.00010 | $0.00263 |
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 4d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- opik-instrument — 100% identical, 40 lines differ
- opik-instrument — 100% identical, 40 lines differ
How it starts
The opening of the file, as written. The whole thing — 126 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 ships with it
3 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.
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.
- 4d ago Changed · +2 lines 8d5e39e7710c
- 28d ago Changed · -28 lines f9ed1944734f
- 1mo ago Changed · +5 lines 1050ff525e8e
- 1mo ago Changed · +11 lines 0994133122af
- 1mo ago Changed · +1 lines 37448b1870dd
- 1mo ago First seen · 135 lines · 101 tokens per session scan A ac951dfe54c3
opik-instrument is a skill published in the GitHub repository comet-ml/opik-mcp (225 stars, last pushed today), licensed Apache-2.0. It adds 101 tokens to every session and 2,630 once invoked, about $0.0004 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
cqlib-kernel
A controlled workflow for running a cqlib quantum-style angle kernel and quantum support vector machine (QSVM), a classifier that separates labelled data. It compares the result with independent mathematical and RBF baselines and states the method's scientific limits.
qiskit-machine-learning
A Qiskit Machine Learning coding skill for quantum kernels, quantum support-vector models, quantum neural networks, gradients, training, and prediction. It uses quantum circuits as part of machine-learning models.
squlearn-learning
A Python toolkit that connects quantum circuits and measurements with scikit-learn, a common machine-learning library. It supports quantum kernels, which compare data using quantum circuits, and scikit-learn estimators.
local-rag-search
Efficiently perform web searches using the mcp-local-rag server with semantic similarity ranking. Use this skill when you need to search the web for current information, research topics across multiple sources, or gather context from the internet without using external APIs. This skill teaches effective use of…
luma-vision
A skill for analyzing images with several external vision models. It is activated only when a user starts a request with /skill luma-vision and includes an image.
research-topic
Multi-step research orchestration. Use when user asks "research X", "summarize current state of Y", "what's the latest on Z", or compares approaches. Calls extract(action="agent") which searches the web, extracts top results, then synthesises a citation-preserving Markdown answer with one configured LLM.