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 commands/jcarlosrodicio/opencode-agent-orchestration-kit/evolvegit 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.00019 | $0.01501 |
| Opus 5 | $0.00010 | $0.00750 |
| Sonnet 5 | $0.00004 | $0.00300 |
| Haiku 4.5 | $0.00002 | $0.00150 |
Grade A, and why
evolve 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 2d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolve the OpenCode harness:
$ARGUMENTS
Run the AHE flow that matches the requested scope. The full flow remains mandatory for real harness changes; audit-only branches have explicit stop conditions. This is for agents, commands, skills, tools, workflows, or harness memory, not app features.
Preconditions
- Check whether the harness is in git with
git status. - If git is unavailable, do not promise automatic rollback.
- Identify or create the target iteration path under
docs/ai/evolution/runs/iteration-XXX/.
Init/context policy
Before evaluating or proposing harness changes, record:
cwd: must be the OpenCode harness repo.AGENTS.md: local rules and evolution boundaries.git state: branch, pending changes, and real rollback ability.validation commands:node scripts/check-harness.mjs,node --test scripts/check-harness.test.mjs, and needed replays.- validation expectations:
node scripts/check-harness.mjsis the cheap local smoke check;node --test scripts/check-harness.test.mjsis the long checker suite and should run with an explicit time budget above the default harness timeout, record observed runtime, and not be classified as a functional failure only because cancellation happened near the time ceiling.
repo docs:docs/ai/harness/,docs/ai/evolution/,mechanisms.jsonl,rejected_mechanisms.jsonl,session-sources.md, and benchmarks.
Session Sources
/evolve is OpenCode-first. Its local default source is:
~/.local/share/opencode/opencode.db
The primary evidence unit is an execution tree, not a flat standalone session:
- one root session with
parent_id = null - all child sessions and descendants linked through
parent_id
session_sources may add optional raw exports from:
RAW_SESSIONS_DIR/raw-sessions
Before invoking evaluator, stage normalized evidence with:
node scripts/collect-session-evidence.mjs --iteration iteration-XXX
The collector should emit:
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.
- 2d ago First seen · 168 lines · 19 tokens per session scan A a6860ebcb33b
evolve is a command published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (105 stars, last pushed 4d ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,501 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 commands, from other repositories
execute-parallel
Spawn N concurrent /ai-sdlc execute sessions in tmux panes (max 5). Reads the dispatch-ready frontier, presents top N candidates, asks operator to confirm, then fires one tmux window per task. Coordination via .ai-sdlc/dispatch/sessions/. Resource-gated: refuses if available memory = ncpu. AISDLC-462.
looper
Design and scaffold a Looper agent loop.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).
loop
The loop pack is dxkit's deterministic preflight/postflight layer for autonomous coding loops — a Claude Code session that keeps working until it decides to stop. It stops a loop from declaring "done" while it has introduced net-new findings, by re-running the guardrail on every Stop and feeding any net-new findings…
selfloop
Start or control a persistent SIPS loop whose only objective is improving SIPS and the agent operating it through measured, verified iterations.
evolution-engine
Scan feedback and generate evolution proposals for rule/skill upgrades.