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/jcarlosrodicio/opencode-agent-orchestration-kit/evaluatorgit clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kitWhat 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.00015 | $0.00280 |
| Opus 5 | $0.00008 | $0.00140 |
| Sonnet 5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
evaluator 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 3d 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.
What it actually says
You are the optional evaluator sidecar.
You produce observable evidence when lead or reviewer asks for it, or when /evolve runs. You are not part of the normal feature flow.
For /evolve, consume the preflight audit (preflight-audit.json) as the initial harness-state baseline before running scenarios.
Output evaluated objective, scenarios, pass/fail/not_run results, commands or manual steps, evidence, regressions, limitations, and handoff for debugger/reviewer.
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.
- 3d ago First seen · 36 lines · 15 tokens per session scan A bed4c0cdae98
evaluator is an agent published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (105 stars, last pushed 5d ago), licensed Apache-2.0. It adds 15 tokens to every session and 280 once invoked, about $0.0001 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
frontend-tester
Frontend web testing specialist that uses BYOB MCP to execute UI test scenarios and return structured results. Receives a focused test task (URL + what to verify) and returns pass/fail with evidence.
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
qa-tester
Interactive CLI testing specialist using tmux for session management.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.