d30a4c0d38
15 categories: design, engineering, game-development, marketing, paid-media, product, project-management, sales, spatial-computing, specialized, strategy, support, testing, examples, integrations. Each agent has frontmatter (name, description, color, emoji, vibe) and a detailed system prompt. Source: msitarzewski/agency-agents (MIT). These feed into our content pipeline: agent personas drive strategy and content generation through MixPost Enterprise, Bio.Host, and the wider Host UK toolkit via MCP. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
OpenCode Integration
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, copy them to your OpenCode config directory:
mkdir -p ~/.config/opencode/agents
cp integrations/opencode/agents/*.md ~/.config/opencode/agents/
Regenerate
./scripts/convert.sh --tool opencode