oh-my-opencode-slim is a plugin that coordinates multiple specialized AI agents inside OpenCode, assigning codebase exploration, documentation research, architecture review, design, and implementation to different agents. It is for developers who want agent teams to divide and reconcile software-development work while mixing models from different providers. The catalogue entries are the plugin’s bundled agents, skills, and instruction.
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/alvinunreal/oh-my-opencode-slim/domaingit clone --depth 1 https://github.com/alvinunreal/oh-my-opencode-slimWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/alvinunreal/oh-my-opencode-slim/domain)<a href="https://agentmods.dev/agents/alvinunreal/oh-my-opencode-slim/domain"><img src="https://agentmods.dev/badge/agents/alvinunreal/oh-my-opencode-slim/domain.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.00392 |
| Opus 5 | $0.00000 | $0.00196 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
domain 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 6d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- domain — 88% identical, 32 lines differ
- domain — 84% identical, 30 lines differ
- domain — 84% identical, 33 lines differ
- domain — 84% identical, 27 lines differ
- domain — 84% identical, 30 lines differ
- domain — 84% identical, 30 lines differ
- domain — 84% identical, 30 lines differ
- domain — 83% identical, 29 lines differ
What it actually says
Domain Docs
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Before exploring, read these
CONTEXT.mdat the repo root — the project's domain glossary and architecture narrative.docs/adr/at the repo root — read ADRs that touch the area you're about to work in.codemap.mdat the repo root — the repo's own architecture map (referenced byAGENTS.md); read it for module responsibilities and integration points before deep work in a folder.
If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them upfront. The /domain-modeling skill (reached via /grill-with-docs and /improve-codebase-architecture — external skills, not bundled in this repo) creates them lazily when terms or decisions actually get resolved.
Use the glossary's vocabulary
When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.
If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for /domain-modeling).
Triage and labels
Operational triage roles and their repo labels are documented in
docs/agents/triage-labels.md (source of truth) and docs/maintainers.md.
The external-PR triage policy lives in docs/agents/issue-tracker.md.
Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
Contradicts ADR-001 (session reflection mode) — but worth reopening because…
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.
- 6d ago First seen · 30 lines · 0 tokens per session scan A 13c3f7f00367
domain is an agent published in the GitHub repository alvinunreal/oh-my-opencode-slim (8,632 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 392 tokens. 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
index
FlowDeck runs a 12-agent system coordinated by an orchestrator. All agent configurations live in src/agents/. Agent definitions use YAML frontmatter (description, mode, model, temperature). The orchestrator selects specialists based on context and delegates work through the OpenCode SDK delegate tool.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and specs (you may know a spec as a PRD) for this repo live as markdown files in .scratch/.
tracer
Evidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendations.
executor
Focused task executor for implementation work (Sonnet).