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-diagnosegit 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-diagnose)<a href="https://agentmods.dev/skills/comet-ml/opik-claude-code-plugin/opik-diagnose"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-claude-code-plugin/opik-diagnose/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-diagnose"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-claude-code-plugin/opik-diagnose.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.00187 | $0.04100 |
| Opus 5.5 | $0.00075 | $0.01640 |
| Sonnet 5.5 | $0.00037 | $0.00820 |
| Haiku 4.5 | $0.00019 | $0.00410 |
Grade A, and why
opik-diagnose 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 26d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose — Surface the Traces Worth Attention
Definition of done: a ranked shortlist of the online/production traces (and Diagnostics issues) worth attention, each carrying the signal that flagged it and its trace id, scoped to a project and a recent window, and ready to hand to /opik-explain. "Worth attention" means errored, slow, regressed, or low online-eval score — not a dump of every trace, and never offline experiment results. If the project can't be read, stop at the first genuine blocker and return one next step.
Operate: rank by real signal over live data, surface the few things worth a look, hand the top one to /opik-explain — and change no code. This skill is read-only by design.
Inputs
The entry point is /opik-diagnose (the current project), /opik-diagnose <project>, or /opik-diagnose <what to look for> (e.g. "slow traces", "errors today"). Infer the rest; treat these as optional overrides:
- project (default: inferred from config/repo) · window (default: recent) · signal focus (default: all — errors, latency, regressions, low scores) · shortlist size (default: a handful).
Ask only at a genuine, non-inferable blocker (see Blockers).
Activation — the only in-scope work
1. Resolve scope
Project (from config/repo) + a recent window. Confirm Opik is reachable: if ~/.opik.config exists or OPIK_API_KEY is set, use it. Otherwise → Blocker ("run opik configure, then rerun").
2. Read the project once, for the shape of the week
With the Opik MCP connected, read('project', <name or id>) costs one call
and answers three things the rest of this skill would otherwise guess: whether
anything is wrong at all (error rate and latency against the previous 7 days —
a flat week is worth saying so and stopping), which score names the project
actually records (the ones worth filtering on later; guessing a name returns an
empty result that reads like good news), and what the project contains.
A rate reported as null means no traces in the window, not a healthy zero.
If the window is quiet, widen it with since="30d" before concluding anything.
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.
- 26d ago First seen · 189 lines · 187 tokens per session scan A 2fa004b8ff25
opik-diagnose is a skill published in the GitHub repository comet-ml/opik-claude-code-plugin (23 stars, last pushed 11d ago), licensed Apache-2.0. It adds 187 tokens to every session and 4,100 once invoked, about $0.0007 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-09-22.
Other skills, from other repositories
troubleshooting-assistant
Diagnoses and resolves MCP server registration failures, GPU detection, BigQuery authentication, index build failures, import errors, search quality issues, and performance problems.
log-structured
USE WHEN auditing logging in a legacy codebase, after adopting the JSON-lines spec, or when user asks to clean up logging. Finds print/console.log/interpolated logger calls and suggests spec- compliant replacements per AGENTS.md. Read-only — never auto-rewrites. Templates per language in templates/logging/.
doctor
Health probe across the worker, embedder, summarizer, queue, vector index, schema, cross-AI wiring and plugin install (cache and live versions). Use when the user types /captain-memo:doctor or when something seems wrong.
log-correlation
Correlates and troubleshoots logs across OS (Linux/macOS), AWS (CloudWatch, CloudTrail, ALB, Lambda), application (JSON, logfmt), and web servers (Nginx, Apache).
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"…
tools-unity-sentry
Sentry Unity SDK integration patterns for error tracking, performance monitoring, transactions, spans, and custom instrumentation.