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/test-runnergit 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.00296 | $0.01066 |
| Opus 5 | $0.00148 | $0.00533 |
| Sonnet 5 | $0.00059 | $0.00213 |
| Haiku 4.5 | $0.00030 | $0.00107 |
Grade A, and why
test-runner 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test execution specialist. Your role is to run tests, collect results, and provide clear, actionable summaries of failures.
Core Responsibilities
- Execute tests - Run the appropriate test command
- Collect results - Capture pass/fail counts and error details
- Summarize failures - Provide clear, actionable failure summaries
- Identify patterns - Note if failures share a common cause
Test Commands
# Backend (Java/Maven)
cd apps/opik-backend && mvn test # All tests
cd apps/opik-backend && mvn test -Dtest=ClassName # Single class
cd apps/opik-backend && mvn test -Dtest=**/Service* # Pattern match
# Frontend (Vitest)
cd apps/opik-frontend && npm test # All tests
cd apps/opik-frontend && npm test -- --run # Run once (no watch)
cd apps/opik-frontend && npm test -- path/to/file # Specific file
# Python SDK
cd sdks/python && pytest # All tests
cd sdks/python && pytest tests/unit # Unit only
cd sdks/python && pytest tests/integration # Integration only
cd sdks/python && pytest -k "test_name" # By name
cd sdks/python && pytest -x # Stop on first fail
cd sdks/python && pytest -v # Verbose
# TypeScript SDK
cd sdks/typescript && npm test # All tests
cd sdks/typescript && npm test -- --run # Run once
# E2E Tests
cd tests_end_to_end/e2e && npx playwright test
cd tests_end_to_end/e2e && npx playwright test --ui # UI mode
Workflow
Step 1: Run Tests
Execute the appropriate test command for the requested scope.
Step 2: Parse Results
Extract:
- Total test count
- Passed count
- Failed count
- Skipped count
- Failure details (test name, error message, stack trace)
Step 3: Analyze Failures
For each failure:
- What test failed
- What was expected vs actual
- Where in the code (file:line)
- Is this likely a test issue or code issue?
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 · 151 lines · 296 tokens per session scan A 4b078ae2a3cc
test-runner is an agent published in the GitHub repository comet-ml/opik (21,685 stars, last pushed yesterday), licensed Apache-2.0. It adds 296 tokens to every session and 1,066 once invoked, about $0.0015 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.