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-verifygit 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-verify)<a href="https://agentmods.dev/skills/comet-ml/opik-claude-code-plugin/opik-verify"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-claude-code-plugin/opik-verify/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-verify"><img src="https://agentmods.dev/badge/skills/comet-ml/opik-claude-code-plugin/opik-verify.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.00145 | $0.03963 |
| Opus 5.5 | $0.00058 | $0.01585 |
| Sonnet 5 | $0.00029 | $0.00793 |
| Haiku 4.5 | $0.00015 | $0.00396 |
Grade A, and why
opik-verify 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 today.
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-verify — 51 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify — Ship or Hold, Against a Policy You Can Read
Definition of done: one verdict — ship, hold, needs_review, or insufficient_evidence — computed from a declared policy over the baseline-vs-candidate numbers, with every criterion listed with its threshold, the observed value, and pass/fail, the cases behind any failure named, and the compare-view link. The policy is either the repo's opik-release-policy.yaml or the documented defaults, and the report says which. If the two runs can't be read or aren't comparable, stop at the first genuine blocker and return exactly one next step. "Looks good to me" is not a verdict; a verdict without its criteria is not one either.
Operate: apply the policy mechanically, show your arithmetic, refuse to ship on a judge nobody validated, and change no application code. The only file this skill may write is the policy file, and only when the user says so. It never deploys.
Inputs
The entry point is /opik-verify right after /opik-compare (its baseline and candidate), /opik-verify <suite> (the two most recent runs on the suite), or /opik-verify <baseline-id> <candidate-id>. Infer the rest; treat these as optional overrides:
- policy (default:
opik-release-policy.yamlat the repo root or under.opik/, else the defaults below) · which experiments (default: as above) ·--record(default: off — write the verdict into the candidate experiment's config).
Ask only at a genuine, non-inferable blocker (see Blockers).
The policy
Every key is optional; missing keys take these defaults. Say in the report which source applied.
# opik-release-policy.yaml — repo root or .opik/. Versioned with the code so the gate is reproducible.
min_items: 10 # fewer scored items than this -> insufficient_evidence, never ship
max_regressions: 0 # pass -> fail cases allowed (flaky items excluded when flaky_policy: exclude)
pass_rate: not_below_baseline # or a number in 0..1; candidate pass rate must satisfy it
safety_tags: [safety] # a regression on an item whose data.tags contains one of these -> hold, always
subgroup_key: null # a data key (e.g. "category"); no subgroup's pass rate may fall
latency_p90_max_increase: 0.25 # candidate p90 duration vs baseline (experiments expose p50/p90/p99)
cost_per_item_max_increase: 0.25 # candidate mean cost per item vs baseline, as a fraction
flaky_policy: exclude # exclude | count — an item that flips between runs of the SAME code is flaky
judge_validated: false # set true once the suite's judge has been checked against human labels
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.
- today First seen · 166 lines · 145 tokens per session scan A 002d16c85bee
opik-verify is a skill published in the GitHub repository comet-ml/opik-claude-code-plugin (23 stars, last pushed today), licensed Apache-2.0. It adds 145 tokens to every session and 3,963 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to opik-verify, differing in 51 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"…
huggingface_hub
Discover open machine learning models on Hugging Face Hub via the public model search API.
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"…
AgentDB Learning Plugins
Create and train AI learning plugins with AgentDB's 9 reinforcement learning algorithms. Includes Decision Transformer, Q-Learning, SARSA, Actor-Critic, and more. Use when building self-learning agents, implementing RL, or optimizing agent behavior through experience.