Top-of-file note in integrations/opencode/README.md: copying source .md files into .opencode/agents/ fails OpenCode schema validation; run scripts/install.sh --tool opencode, which resolves named colors to hex and omits the tools field. Follow-up to #832 / #796. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
OpenCode Integration
❌ Don't do this:
# WRONG — will fail with schema validation errors cp agency-agents/engineering/*.md .opencode/agents/✅ Do this instead:
/path/to/agency-agents/scripts/install.sh --tool opencodeThe source files use named colors and a
toolsfield that OpenCode rejects. The installer converts them to#RRGGBBhex and strips incompatible fields automatically.
OpenCode agents are .md files with YAML frontmatter stored in
.opencode/agents/. The converter maps named colors to hex codes and adds
mode: subagent so agents are invoked on-demand via @agent-name rather
than cluttering the primary agent picker.
Install
# Run from your project root
cd /your/project
/path/to/agency-agents/scripts/install.sh --tool opencode
This creates .opencode/agents/<slug>.md files in your project directory.
Activate an Agent
In OpenCode, invoke a subagent with the @ prefix:
@frontend-developer help build this component.
@reality-checker review this PR.
You can also select agents from the OpenCode UI's agent picker.
Agent Format
Each generated agent file contains:
---
name: Frontend Developer
description: Expert frontend developer specializing in modern web technologies...
mode: subagent
color: "#00FFFF"
---
- mode: subagent — agent is available on-demand, not shown in the primary Tab-cycle list
- color — hex code (named colors from source files are converted automatically)
Project vs Global
Agents in .opencode/agents/ are project-scoped. To make them available
globally across all projects, first generate the agent files, then install
with --path:
./scripts/convert.sh --tool opencode
./scripts/install.sh --tool opencode --path ~/.config/opencode/agents
Regenerate
./scripts/convert.sh --tool opencode