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 agentmods add skills/comet-ml/opik-claude-code-plugin/agent-opsnpx skills add comet-ml/opik-claude-code-plugin --skill agent-opsgit clone --depth 1 https://github.com/comet-ml/opik-claude-code-pluginWhat 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 | $0.00076 | $0.00947 |
| Opus 5 | $0.00038 | $0.00474 |
| Sonnet 5 | $0.00015 | $0.00189 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
agent-ops 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Operations: Build, Evaluate, and Monitor AI Agents
This skill covers the agent lifecycle beyond basic tracing: architecture patterns, evaluation, metrics, and production monitoring. All examples use Opik for observability — for SDK details (tracing, integrations, span types), load the opik skill.
The Agent Lifecycle
- Instrument — Add Opik tracing to make your agent's behavior visible (see
opikskill) - Evaluate — Measure performance with datasets, metrics, and experiments
- Monitor — Track quality, cost, and reliability in production
- Optimize — Improve based on data from evaluation and production traces
Agent Architecture Patterns
Trace every component of your agent with appropriate span types:
import opik
@opik.track(name="research_agent")
def agent(query: str) -> str:
plan = plan_action(query) # general span
results = execute_tool(plan) # tool span
return generate_response(results) # llm span
@opik.track(type="tool")
def execute_tool(action: dict) -> str:
return search_web(action["query"])
@opik.track(type="llm")
def generate_response(context: str) -> str:
return llm_call(context)
What to Trace
| Component | Span Type | Key Data |
|---|---|---|
| Planning | general |
Reasoning steps, decisions |
| Tool calls | tool |
Tool name, parameters, results |
| LLM calls | llm |
Prompt, response, tokens |
| Retrieval | tool |
Query, documents |
| Validation | guardrail |
Check results, pass/fail |
Evaluation
Evaluate agents at multiple levels — end-to-end and per-component:
from opik.evaluation import evaluate
from opik.evaluation.metrics import AnswerRelevance, Hallucination, AgentTaskCompletion
results = evaluate(
experiment_name="agent-v2",
dataset=dataset,
task=lambda item: {"output": agent(item["input"])},
scoring_metrics=[
AnswerRelevance(),
Hallucination(),
AgentTaskCompletion(),
]
)
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.
- 2d ago First seen · 107 lines · 76 tokens per session scan A 7f24c1ec849b
agent-ops is a skill published in the GitHub repository comet-ml/opik-claude-code-plugin (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 947 once invoked, about $0.0004 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.
Other skills, from other repositories
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
r3f-animation
React Three Fiber animation - useFrame, useAnimations, spring physics, keyframes. Use when animating objects, playing GLTF animations, creating procedural motion, or implementing physics-based movement.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
golden-rss
Use when testing the rss golden build.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.