Files
Wesam Abousaid a3f328c043 docs: refresh for OpenCode v1.17.13, add Go coverage, and rebrand
- Bump every version pin, pricing table, and model ID to the verified
  2026-07-05 state (v1.17.13): Claude Fable 5 / Sonnet 5 on Zen, new
  free tier, deprecation sunset table, v1.17.x changelog section
- Cover gaps: OpenCode Go vs Zen billing, Anthropic subscription-login
  removal (PR #18186), MCP resources, --mini mode, --auto flag, yolo mode
- Fix correctness bugs: command-template !`cmd` syntax in docs and
  .opencode/commands, protect-secrets regex missing 'cat .env', dual
  plugin exports, quickstart PATH fix, Playwright MCP flags, ctrl+d
  keybind conflict, agent/command required-field claims
- Fix links: cursor.com, windsurf.com, platform.claude.com,
  code.claude.com, opencode.ai/discord, Vercel Grep announcement
- Rebrand: banner (Images/banner.svg), 1280x640 social preview asset,
  hero redesign with star CTA, ecosystem stats, private vulnerability
  reporting channel, CI-matching local checks, MD060 lint opt-out
2026-07-05 14:11:51 +02:00
..

Specialized Agents

Starting points, not authoritative wisdom. These are one set of defensible defaults for common engineering roles — copy them to .opencode/agents/<name>.md and edit them to match your stack, your conventions, and your taste. They encode opinions that a senior engineer on your team might disagree with, which is fine — the value is having a coherent starting point, not in any one rule being universally right.

When something in a prompt says "always X, never Y," read it as "by default, X — but override per project in your AGENTS.md if Y is correct for you."

How to use

Each role has:

  • A system prompt under system-prompts/ — copy verbatim or as a starting point
  • A short description under descriptions/ — what the role focuses on and when to reach for it

To install one in your project:

mkdir -p .opencode/agents
cp specialized-agents/system-prompts/code-reviewer-prompt.md .opencode/agents/code-reviewer.md

The filename you choose becomes the agent's mention name (@code-reviewer).

You can also reference the prompt file from opencode.json without copying:

{
  "agent": {
    "code-reviewer": {
      "description": "Senior code reviewer",
      "mode": "subagent",
      "model": "anthropic/claude-sonnet-5",
      "prompt": "{file:./specialized-agents/system-prompts/code-reviewer-prompt.md}",
      "permission": { "edit": "deny" }
    }
  }
}

⚠️ Warning: {file:...} inlines the file verbatim — including its YAML frontmatter — into the system prompt. Strip the frontmatter block from the copy you reference this way.

Available roles

Role Mode Reach for it when… Prompt Description
Code Reviewer subagent Surface bugs / security / perf / maintainability in a diff or branch prompt description
Security Reviewer subagent Audit code for OWASP-style vulnerabilities prompt description
Backend Engineer all (primary + subagent) TypeScript/Go/Python API work, DB integration, REST/GraphQL prompt description
Frontend Engineer all (primary + subagent) React/Tailwind/TypeScript UI work, accessibility, component design prompt description
Tech Lead all (primary + subagent) Architectural decisions, cross-team trade-offs, sequencing work prompt description
UX Engineer all (primary + subagent) Component-first UI work, design-system alignment prompt description
Database Engineer all (primary + subagent) Schema design, migrations, query performance prompt description

💡 These are starting points. Edit the prompts to match your stack — replace generic guidance with your actual conventions, technologies, and naming.

Patterns

Sequential review

[build] > implement the OAuth refresh endpoint
[build] > @code-reviewer review the changes
[build] > @security-auditor audit the same files
[build] > address the high-severity findings

Parallel research

> @backend-engineer  propose a migration plan for the payments service
> @database-engineer review the schema implications
> @tech-lead         decide which proposal to ship

Persistent specialist primary

For ongoing work in a single area, install a role as a primary agent (mode: primary or mode: all) so it's a Tab target.

cp specialized-agents/system-prompts/frontend-engineer-prompt.md .opencode/agents/frontend.md
# Edit the frontmatter to `mode: primary`, then Tab in the TUI cycles
# [build] ↔ [plan] ↔ [frontend]

Customizing

Three things to adapt before using these in earnest:

  1. Tech stack lines — the prompts mention "TypeScript, React, Tailwind" etc. Replace with your actual stack.
  2. Repo-specific conventions — point at your AGENTS.md and let it carry the conventions.
  3. Permission profiles — every role's permission map is conservative by default. Loosen bash patterns for commands your team runs constantly.

The prompts are MIT-licensed (same as the repo). Fork them.