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 instructions/comet-ml/opik/copilot-instructionsgit clone --depth 1 https://github.com/comet-ml/opikWhat 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.05043 | $0.05043 |
| Opus 5 | $0.02521 | $0.02521 |
| Sonnet 5 | $0.01009 | $0.01009 |
| Haiku 4.5 | $0.00504 | $0.00504 |
Grade A, and why
opik copilot-instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Code Review Instructions
Scope: These guidelines apply to all Opik applications including backend, frontend, and SDKs. Use the appropriate sections based on the code being reviewed.
When Copilot automatically reviews pull requests, use the following guidelines to structure feedback and ensure consistency across the entire Opik project.
Project Overview
Opik is a comprehensive observability and AI evaluation platform with multiple applications:
- Backend: Java-based REST API with MySQL and ClickHouse databases
- Frontend: React/TypeScript application with modern UI components
- Python SDK: Client library for Python applications
- TypeScript SDK: Client library for TypeScript/JavaScript applications
- Documentation: Comprehensive documentation site
- Testing: End-to-end and load testing suites
1. Git Workflow & Branch Management
Branch Naming Convention
{username}/{ticket}-{summary}
Examples:
andrescrz/OPIK-2236-add-documentation-and-user-facing-distinction-to-pr-template
someuser/issue-1234-some-task
someotheruser/NA-some-other-task
Commit Message Standards
Use component types to categorize changes (optional but recommended):
[DOCS]- Documentation updates, README changes, comments, swagger/OpenAPI documentation[FE]- Frontend changes (React, TypeScript, UI components)[BE]- Backend changes (Java, API endpoints, services)[SDK]- SDK changes (Python, TypeScript SDKs)
Examples:
# ✅ Recommended format
git commit -m "[OPIK-1234] [FE] Add project custom metrics UI dashboard"
git commit -m "[OPIK-1234] [BE] Add create trace endpoint"
# ✅ Also acceptable
git commit -m "[OPIK-1234] Add project custom metrics UI dashboard"
Pull Request Guidelines
Title Format: [{ticket}] [{component}] {summary}
Required Sections:
- Details: What the change does, why it was made, and any design decisions
- Change checklist: User facing and Documentation update checkboxes
- Issues: GitHub issue or Jira ticket references
- Testing: Scenarios covered by tests and steps to reproduce
- Documentation: List of docs updated or new configuration introduced
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.
- yesterday First seen · 577 lines · 5,043 tokens per session scan A f7c1bc10c5e5
opik copilot-instructions.md is an instructions file published in the GitHub repository comet-ml/opik (21,685 stars, last pushed yesterday), licensed Apache-2.0. It adds 5,043 tokens to every session, about $0.0252 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 instructions, from other repositories
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
swarms CLAUDE.md
Instructions for kyegomez/swarms, covering claude.md — swarms framework guide, installation & setup, any provider supported by litellm works, project layout and core primitive: agent.
vellum-assistant AGENTS.md
Instructions for vellum-ai/vellum-assistant, covering vellum assistant — agent instructions, project structure, intellectual honesty, development and dependencies.
Patter AGENTS.md
Instructions for PatterAI/Patter, covering agents.md, non-negotiables (ci and reviewers block on these), before opening a pr, where things live and commits & prs.
LaunchStack CLAUDE.md
Instructions for Deodat-Lawson/LaunchStack, covering claude.md, frontend rules (apps/web, apps/landing) and workflow.
langchain CLAUDE.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.