oh-my-opencode-slim

Configure agents, models, prompts, skills, and MCPs for oh-my-opencode-slim setups.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill oh-my-opencode-slim-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oh-my-opencode-slim
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/oh-my-opencode-slim
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill oh-my-opencode-slim-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tuning an OpenCode agent harness involves scattered config files, prompt override conventions, and preset rules that are easy to get wrong. This Skill guides safe, minimal configuration changes to oh-my-opencode-slim so agents behave the way you want without breaking existing settings. ## Core Features & Use Cases - Agent and Model Tuning: Adjust models, variants, presets, skills, and MCP permissions per built-in agent such as orchestrator, oracle, librarian, explorer, designer, fixer, observer, and council. - Prompt Customization: Append or replace built-in agent prompts using markdown override files, with correct preset-aware lookup order. - Custom Agent Creation: Define narrow specialist agents under agents.<name> with prompt and orchestratorPrompt so the Orchestrator delegates correctly. - Use Case: If the Orchestrator keeps spawning overlapping parallel writers, add a small rule to orchestrator_append.md so future runs enforce explicit file ownership before delegation. ## Quick Start Ask the assistant to review your oh-my-opencode-slim config and propose a cheaper model assignment for the explorer and librarian agents.

Frequently Asked Questions about oh-my-opencode-slim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change the model for a specific agent in oh-my-opencode-slim?

Edit the active preset under `presets.<preset>.<agent>` in `~/.config/opencode/oh-my-opencode-slim.jsonc` and set the `model` and `variant` fields. The change applies on the next OpenCode run, so restart if you need it immediately.

How do I customize a built-in agent prompt in OpenCode?

Create `~/.config/opencode/oh-my-opencode-slim/{agent}_append.md` to append instructions, or `{agent}.md` to fully replace the bundled prompt. Built-in agents do not support `prompt` fields in the JSON config; markdown override files are the supported mechanism.

Can I add custom agents to oh-my-opencode-slim config?

Yes, unknown keys under top-level `agents` become custom agents that support `prompt` and `orchestratorPrompt` directly in config. Give them a narrow job, clear trigger conditions, and only the skills and MCPs they need.

Which config file takes precedence, JSON or JSONC?

The `.jsonc` file at `~/.config/opencode/oh-my-opencode-slim.jsonc` takes precedence over the `.json` version. Project-local overrides in `<project>/.opencode/oh-my-opencode-slim.json` are checked before user-level config.

When should I not create a custom agent?

Avoid custom agents for one-off tasks or when a built-in specialist already covers the job, such as explorer for codebase scouting or librarian for external research. Custom agents work best for narrow, repeatable specialties with clear routing rules.