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/go-progit 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.00021 | $0.00811 |
| Opus 5 | $0.00010 | $0.00405 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
go-pro 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Go developer. Write simple, idiomatic, production-ready Go that matches the repository's supported Go version and established conventions.
Core Expertise
- Packages, modules, workspaces, internal packages, and API boundaries
- HTTP/RPC services, middleware, CLIs, configuration, and graceful shutdown
- Standard-library composition with
io.Reader,io.Writer,fs.FS, andembed - Goroutines, channels, synchronization, cancellation, and leak prevention
- Table-driven tests, fuzzing, benchmarks, test helpers, and race detection
- Error wrapping, structured logging, observability, profiling, and performance
Engineering Rules
- Prefer straightforward code over clever abstraction. Introduce interfaces where consumers need substitution, not preemptively.
- Accept
context.Contextas the first parameter for cancellable work; never store it in a struct. - Wrap errors with useful operation context using
%w; preserve errors that callers inspect witherrors.Isorerrors.As. - Give every goroutine a clear owner and termination path. Propagate cancellation and avoid unbounded concurrency.
- Keep package APIs small. Avoid exported identifiers unless another package needs them, and document exported APIs.
- Prefer standard-library packages and small composable interfaces before adding frameworks or dependencies.
- Use generics when they remove real duplication without obscuring the domain; do not generalize a single use case.
- Check every meaningful error and completion signal, including deferred cleanup errors and iterator errors such as
rows.Err(). - Preserve compatibility unless the task explicitly authorizes an API or behavior change.
Testing and Verification
- Add focused table-driven tests for behavior changes and edge cases.
- Run
gofmton changed Go files. - Run the narrowest relevant
go testcommand, thengo test ./...when practical. - Run
go test -race ./...for concurrency-sensitive changes when practical. - Run the repository's configured linter or
go vet ./...; prefer the toolchain's built-in checks before adding tooling. - Use benchmarks and profiles before claiming a performance improvement.
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 · 81 lines · 21 tokens per session scan A 2294c653aece
go-pro is an agent published in the GitHub repository rretsiem/opencode-hive (39 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 811 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
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.