agents

A set of project instructions that tells coding agents which parts of the Opik project to use and how to work on them. It covers backend, frontend, software libraries, tests, planning, and formatting.

In plain words
What is it for?
Use it to route tasks to the correct project domain, decide when to plan or test first, choose suitable models for different work, and run formatting checks on changed files.
Why use it?
It reduces guesswork in a large codebase by directing each task to the right area and setting consistent working rules.

Cursor rule for Codex

Install

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.

agentmods
npx agentmods add rules/comet-ml/opik/agents
Clone the repo
git clone --depth 1 https://github.com/comet-ml/opik

Made for: Codex.

Per session 350 This file is loaded in full into every session.
When invoked 350 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00350 $0.00350
Opus 5 $0.00175 $0.00175
Sonnet 5 $0.00070 $0.00070
Haiku 4.5 $0.00035 $0.00035

Measured yesterday against content hash 1e9dbd2c1674, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agents 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 yesterday.

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.

.agents/rules/agents.mdc · 34 lines

What it actually says

Agent Deployment

Domain Routing

  • apps/opik-backend/** → Backend skill
  • apps/opik-frontend/** → Frontend skill
  • sdks/opik_optimizer/** → Opik Optimizer skill
  • sdks/python/** → Python SDK skill
  • sdks/typescript/** → TypeScript SDK skill
  • tests_end_to_end/** → Playwright E2E skill

Frontend Structure

  • apps/opik-frontend/src/v2/ → the Opik UI (layout, pages, pages-shared)
  • The legacy src/v1/ tree was removed in OPIK-7105; V2 is the only experience
  • Shared layers: ui/, shared/, api/, types/, store/, hooks/, lib/, constants/, contexts/, plugins/
  • Shared components must not be version-aware (no isV2 props)

Task Approach

  • Complex features → Plan before implementing
  • Bug fixes → Reproduce with test first
  • Multi-component → Coordinate across domains

Execution

  • Independent tasks → Run in parallel
  • Use thinking model (Opus, GPT 5.3, GPT 5.3 High) for: complex planning, security, architecture
  • Use fast model (Haiku, GPT Nano, GPT Codex Low/Medium) for: simple test runs, formatting

Formatting and Linting

  • For local verification and PR iterations, run pre-commit on changed files, not repository-wide file lists.
  • Avoid --all-files unless a cleanup migration explicitly requires repository-wide normalization.
Changes

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.

  1. yesterday First seen · 34 lines · 350 tokens per session scan A 1e9dbd2c1674

Subscribe to this mod's changes

agents is a cursor rule published in the GitHub repository comet-ml/opik (21,685 stars, last pushed yesterday), licensed Apache-2.0. It adds 350 tokens to every session, about $0.0018 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.