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.
git 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/commands/comet-ml/opik-claude-code-plugin/trace-claude-code)<a href="https://agentmods.dev/commands/comet-ml/opik-claude-code-plugin/trace-claude-code"><img src="https://agentmods.dev/badge/commands/comet-ml/opik-claude-code-plugin/trace-claude-code/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/commands/comet-ml/opik-claude-code-plugin/trace-claude-code"><img src="https://agentmods.dev/badge/commands/comet-ml/opik-claude-code-plugin/trace-claude-code.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.00000 | $0.00986 |
| Opus 5.5 | $0.00000 | $0.00394 |
| Sonnet 5.5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
trace-claude-code 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opik Claude Code Session Tracing
This command enables/disables automatic tracing of your Claude Code sessions to Opik.
Based on the user's request: $ARGUMENTS
Scope
Tracing can be enabled at two levels:
- Project (default):
.claude/.opik-tracing-enabledin the current project directory. - Global (
--globalflag):~/.claude/.opik-tracing-enabled, which enables tracing for every project.
The project-level file takes precedence over the global one, so a single project can override the global setting (including turning tracing off while it is enabled globally).
File Semantics
For both the project and global files:
- File contains
offordisabled→ tracing disabled (used to opt a project out of a global enable) - File contains
debug→ tracing + debug logging - File exists with any other content (or empty) → tracing enabled
- File doesn't exist → no opinion at this level (fall through to the next level)
Resolution order (first match wins): project off → project enabled → global enabled → disabled.
Actions
Determine the target file from the flags:
- If
--global(or--user) is present, target is~/.claude/.opik-tracing-enabled. - Otherwise, target is
.claude/.opik-tracing-enabledin the current directory.
If the request contains "start":
- Create the parent
.claude/directory if needed withmkdir -p. - If
--debugis present, writedebugto the target file. - Otherwise, write an empty file /
touchthe target file (content doesn't matter). - Confirm scope: "Opik session tracing enabled [globally for all projects | for this project]. Takes effect immediately for new conversation turns."
If the request contains "stop":
- If
--globalis present: delete~/.claude/.opik-tracing-enabled. Confirm: "Opik session tracing disabled globally." - Otherwise (project stop):
- Check whether the global file
~/.claude/.opik-tracing-enabledexists and is not itselfoff/disabled. - If global tracing is active, write
offto.claude/.opik-tracing-enabled(an explicit opt-out that overrides the global enable), and confirm: "Opik session tracing disabled for this project (overriding the global setting)." - If global tracing is not active, delete
.claude/.opik-tracing-enabled, and confirm: "Opik session tracing disabled for this project."
- Check whether the global file
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.
- 1mo ago First seen · 88 lines · 0 tokens per session scan A 5e0c8fd8f888
trace-claude-code is a command published in the GitHub repository comet-ml/opik-claude-code-plugin (23 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 986 tokens. 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 commands, from other repositories
doctor
Check OCR installation and verify all dependencies are available.
flaky-test
Diagnose a flaky test by running it N times. Delegates to flaky-test-isolator subagent — N runs, signature-grouped failures, stability report. Does NOT fix the test.
doctor
Diagnose WhatsApp MCP setup — bridge health, auth, pairing, and which account each server points to.
perf
Structured performance investigation with baselines, profiling, and evidence-backed decisions.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
inventory
Codebase inventory skill — scans the repo for a named pattern (inline SQL, fetch calls, feature flags, debug leftovers, deprecated APIs, etc.) and emits a structured Markdown inventory cross-referenced with framework metadata (routes, handlers). Language-agnostic and pack-driven — the engine matches whatever a YAML…