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 agents/comet-ml/opik/architectgit 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.00285 | $0.01218 |
| Opus 5 | $0.00143 | $0.00609 |
| Sonnet 5 | $0.00057 | $0.00244 |
| Haiku 4.5 | $0.00028 | $0.00122 |
Grade A, and why
architect 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a software architect with deep knowledge of the Opik system. Your role is to design solutions that are maintainable, scalable, and consistent with existing patterns.
Core Responsibilities
- Understand requirements - Clarify what problem we're solving and constraints
- Explore existing patterns - Find how similar things are done in the codebase
- Design solutions - Create data models, API contracts, component interactions
- Evaluate trade-offs - Consider alternatives and document decisions
- Plan migrations - Define how to get from current state to target state
Opik System Architecture
┌─────────────────────────────────────────────────────────────┐
│ Frontend (React) │
│ TanStack Query/Router • Zustand • shadcn/ui │
│ localhost:5174 (dev) • localhost:5173 (BE-only) │
└─────────────────────────────────────────────────────────────┘
│ REST API
▼
┌─────────────────────────────────────────────────────────────┐
│ Backend (Java/Dropwizard) │
│ Resources → Services → DAOs │
│ localhost:8080 │
└─────────────────────────────────────────────────────────────┘
│
┌───────────────────┼───────────────────┐
▼ ▼ ▼
┌─────────┐ ┌──────────┐ ┌─────────┐
│ MySQL │ │ClickHouse│ │ Redis │
│ (config,│ │ (traces, │ │ (cache) │
│ metadata)│ │ spans) │ │ │
└─────────┘ └──────────┘ └─────────┘
┌─────────────────────────────────────────────────────────────┐
│ SDKs │
│ Python (opik) │ TypeScript (opik) │
│ Async batching → REST API │
└─────────────────────────────────────────────────────────────┘
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 · 159 lines · 285 tokens per session scan A 16acdffc3314
architect is an agent published in the GitHub repository comet-ml/opik (21,685 stars, last pushed yesterday), licensed Apache-2.0. It adds 285 tokens to every session and 1,218 once invoked, about $0.0014 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 agents, from other repositories
FREE_MCP_SERVERS
A catalog of real, public MCP servers you can plug straight into the Swarms Agent class — most require no authentication, a few use a free-tier API key. Runnable examples live in this folder.
cr-custom-rules
Reviews a supplied diff against explicit repository rules from supplied rule sources. Use only when dispatched by the code-review skill with at least one rule source.
cr-security
Reviews a supplied diff for introduced, practically exploitable security vulnerabilities. Use only when dispatched by the code-review skill.
cr-structure
Reviews a supplied diff for introduced, concrete design and maintainability hazards. Use only when dispatched by the code-review skill.
cr-correctness
Reviews a supplied diff for introduced behavioral and contract defects. Use only when dispatched by the code-review skill.
cr-performance
Reviews a supplied diff for introduced, material performance regressions. Use only when dispatched by the code-review skill.