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
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/alvinunreal/oh-my-opencode-slim/reflect)<a href="https://agentmods.dev/skills/alvinunreal/oh-my-opencode-slim/reflect"><img src="https://agentmods.dev/badge/skills/alvinunreal/oh-my-opencode-slim/reflect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alvinunreal/oh-my-opencode-slim/reflect"><img src="https://agentmods.dev/badge/skills/alvinunreal/oh-my-opencode-slim/reflect.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.03086 |
| Opus 5.5 | $0.00021 | $0.01234 |
| Sonnet 5.5 | $0.00011 | $0.00617 |
| Haiku 4.5 | $0.00005 | $0.00309 |
Grade A, and why
reflect 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 9d 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
1 near-identical copy found in the catalogue:
- reflect — 100% identical, 58 lines differ
How it starts
The opening of the file, as written. The whole thing — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflect
Reflect is an orchestrator-only workflow for learning from repeated work. It looks back over recent sessions, project notes, and existing agent assets, then recommends the smallest useful improvement: a skill, custom agent, command, configuration change, prompt rule, documentation playbook, or no change.
The goal is to identify real repeated friction and suggest practical improvements with evidence.
Branch: lines marked [branch: --sessions] run only with that flag; plain /reflect skips Session Mode.
When to Use
Use Reflect when the user asks to:
- run
/reflector/reflect <focus>; - run
/reflect --sessionsfor session archaeology; - learn from recent sessions or repeated workflows;
- find work they keep doing manually;
- improve their oh-my-opencode-slim setup based on actual usage using oh-my-opencode-slim skill;
- review whether a recurring process should become a reusable playbook;
- turn repeated workflow friction into a safer future default.
Do not use Reflect for ordinary implementation work, one-off debugging, broad architecture review, or speculative agent creation without workflow evidence.
Session Mode [branch: --sessions]
When the user includes --sessions in their reflect command, shift to session
archaeology: analyze historical OpenCode sessions across all repos to find
repeated patterns, friction, and improvement opportunities.
Session Discovery
-
Detect the schema, then load recent sessions. OpenCode v2 keeps live data in
session_v2+session_message; legacy v1 databases keepsessionmessage(on v2 hosts those may still exist but are empty leftovers). Detect by probingsession_v2insqlite_masterand select the pair together — never per-table:session_messagecan exist on v1 hosts holding only metadata rows.
Write the probe below to a temp file (for example
/tmp/reflect-sessions.mjs) and runbun /tmp/reflect-sessions.mjs. Do not inline it withbun -e "…": nested quotes get mangled by PowerShell on Windows; a temp script sidesteps shell quoting entirely.
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.
- 9d ago Changed · +2 lines cf4730ba9345
- 11d ago Changed · +36 lines b1e8edb40650
- 1mo ago First seen · 327 lines · 53 tokens per session scan A 3e7edc3d6559
reflect is a skill published in the GitHub repository alvinunreal/oh-my-opencode-slim (9,795 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 3,086 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
context-steward
Full context lifecycle — ingest, filter, 3-pass prune, protect, summarize, persist. Load on demand when executing a prune. Triggers are in context-steward-triggers (alwayson).
session-persistence
Maintain continuity across FlowDeck sessions by loading previous context, checkpointing mid-session state, and writing structured summaries at session end.
context-guard
Protect critical context from pruning during compaction. Preserve active plans, safety files, pending operations, and user intent anchors.
repo-memory-graph
Build and maintain a persistent graph of architecture, conventions, bug history, ownership patterns, and module relationships for this specific codebase.
context-steward-triggers
Auto-loaded context health triggers — thresholds and quick actions. Full 6-step pipeline in context-steward skill (load on demand).
session-flow
Reorient in the current Claude Code session with an evidence-backed map of its goal, pivots, outcomes, current step, and open decisions.