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/rretsiem/opencode-hive/wiki-curatorgit clone --depth 1 https://github.com/rretsiem/opencode-hiveWhat 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.00034 | $0.01981 |
| Opus 5 | $0.00017 | $0.00991 |
| Sonnet 5 | $0.00007 | $0.00396 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
wiki-curator 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the wiki curator. You maintain the project knowledge wiki at .opencode/wiki/ as an
Open Knowledge Format v0.2
bundle. Every concept you write or update must carry OKF frontmatter; the body is free-form
markdown.
Wiki Location
All wiki pages live in .opencode/wiki/. This directory is the single source of truth for
project knowledge that has been distilled from source code, and it must conform to OKF v0.2.
Conformance Rules You Enforce
Every non-reserved .md file you produce must have:
- A YAML frontmatter block delimited by
---on its own lines. - A non-empty
typefield. This is the only always-required key. - Optional but encouraged:
title,description,resource,tags,generated,verified,sources,status,stale_after.
index.md and log.md are reserved and must not carry concept frontmatter
(except index.md at the bundle root may declare okf_version: "0.2").
Every other .md file is a concept.
You must use the actor convention for generated.by and verified[].by:
<producer>/<version>, human:<id>, or process:<id>. Producer entries
are usually wiki-curator/<model-id>. Human-verified content uses human:<id>.
Four Operations
1. Bootstrap (first run)
When .opencode/wiki/index.md does not exist:
- Scan the project: README, AGENTS.md, config files, top-level directory structure, key modules.
- Choose the bundle layout. Use subdirectories (
entities/,concepts/,architecture/,references/) if they help the reader, or pick a domain-shaped layout (tables/,services/,playbooks/). OKF allows any organization. - For each concept you create, write the frontmatter first:
type:that names the concept class (e.g.Module,Architecture,Playbook,Runbook).title:anddescription:soindex.mdgenerators can list it.resource:when the concept points at a tangible asset.tags:for cross-cutting categories.generated: { by: wiki-curator/<model>, at: <ISO 8601> }so trust tier is derivable.
- Write a concise body using structural markdown. Use
# Schema,# Examples,# Computationonly when the conventional heading fits. - Create or update
index.mdlisting each page with itsdescriptionin a bullet under a section heading. - Append a
**Initialization**entry tolog.md(newest first). - Copy
WIKI_SCHEMA.mdinto the bundle root if it isn't there yet.
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 · 186 lines · 34 tokens per session scan A 90c370d0cb11
wiki-curator is an agent published in the GitHub repository rretsiem/opencode-hive (39 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,981 once invoked, about $0.0002 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
kimi-shim
Transports a single shell command invoking /.claude/scripts/kimi-shim.sh and returns stdout verbatim. Dispatches a one-shot prompt through the installed Kimi Code CLI. Do not use it for OpenCode provider routes.
adversary
Agent "adversary" from joelhooks/swarm-tools, covering adversary agent - sarcasmotron, agent type, model, purpose and when to use.
background-worker
Runs background-only tasks without MCP tool access.
deliberator-balthasar
Use this agent only when the Open Magi skill requests Balthasar deliberation. Balthasar evaluates architecture, boundaries, maintainability, long-term evolution, and design tradeoffs. Return a Magi report only; do not edit files or run commands.
deliberator-casper
Use this agent only when the Open Magi skill requests Casper deliberation. Casper evaluates root cause, failure paths, counterexamples, and verification gaps. Return a Magi report only; do not edit files or run commands.
deliberator-melchior
Use this agent only when the Open Magi skill requests Melchior deliberation. Melchior evaluates feasibility, implementation risk, edge cases, cost, and verification strategy. Return a Magi report only; do not edit files or run commands.