Agent Skill
2/7/2026

opencode-agents

Define and configure OpenCode agents with proper permissions, tools, and behaviors. Use for agent creation, tool access control, permission patterns, and mode selection. Use proactively when user says "create an agent", "agent permissions", "tool access", "subagent", "restrict agent", or asks about agent configuration. Examples: - user: "Create a security reviewer agent" → design agent with read-only permissions, appropriate skills - user: "How do I restrict bash access?" → explain permission.bash patterns with allow/ask/deny - user: "Make an agent use the question tool" → configure tools.question: "enabled" or ensure no tools restrictions - user: "What's the difference between primary and subagent?" → explain mode options

J
justinlevinedotme
6GitHub Stars
1Views
npx skills add justinlevinedotme/jalco-opencode

SKILL.md

Nameopencode-agents
DescriptionDefine and configure OpenCode agents with proper permissions, tools, and behaviors. Use for agent creation, tool access control, permission patterns, and mode selection. Use proactively when user says "create an agent", "agent permissions", "tool access", "subagent", "restrict agent", or asks about agent configuration. Examples: - user: "Create a security reviewer agent" → design agent with read-only permissions, appropriate skills - user: "How do I restrict bash access?" → explain permission.bash patterns with allow/ask/deny - user: "Make an agent use the question tool" → configure tools.question: "enabled" or ensure no tools restrictions - user: "What's the difference between primary and subagent?" → explain mode options

name: opencode-agents description: |- Define and configure OpenCode agents with proper permissions, tools, and behaviors. Use for agent creation, tool access control, permission patterns, and mode selection.

Use proactively when user says "create an agent", "agent permissions", "tool access", "subagent", "restrict agent", or asks about agent configuration.

Examples:

  • user: "Create a security reviewer agent" → design agent with read-only permissions, appropriate skills
  • user: "How do I restrict bash access?" → explain permission.bash patterns with allow/ask/deny
  • user: "Make an agent use the question tool" → configure tools.question: "enabled" or ensure no tools restrictions
  • user: "What's the difference between primary and subagent?" → explain mode options

<overview>

Define specialized agents with precise tool access and permissions.

</overview> <rules>

Agent Fundamentals

Location

ScopePath
Project.opencode/agent/<name>.md
Global~/.config/opencode/agent/<name>.md

Agents MAY also be defined in opencode.json:

{
  "agent": {
    "my-agent": {
      "description": "Brief description",
      "mode": "subagent",
      "model": "anthropic/claude-sonnet-4-20250514"
    }
  }
}

Frontmatter Schema

FieldTypeDefaultDescription
descriptionstringREQUIREDTrigger description (see below)
modestring"all"primary, subagent, or all
modelstringinheritedModel override (e.g., anthropic/claude-opus-4-5)
temperaturenumber1.00.0-2.0, lower = deterministic
maxStepsnumber100Maximum tool calls per turn
disablebooleanfalseDisable without deleting
toolsobjectall enabledTool-specific enable/disable
permissionobjectall allowedPermission restrictions
</rules> <guidelines>

Agent Modes

ModeVisible in MenuTask Tool TargetUse Case
primaryYesNoUser-facing, main agents
subagentNoYesOrchestrated by other agents
allYesYesVersatile, both contexts

Description Guidelines

ModeDescription Style
primary3 words max (shown in TUI menu)
subagentMUST include trigger examples for task tool routing
allBoth: short label + trigger examples

Subagent description example:

description: |-
  Security vulnerability scanner. Use for code audits, dependency checks, and security reviews.
  
  Examples:
  - user: "Review this code for security issues" → scan for vulnerabilities
  - user: "Check for hardcoded secrets" → search for credentials
</guidelines> <rules>

Permission System

CRITICAL: By default, agents have ALL tools and permissions. Only add permission blocks to RESTRICT access.

Permission Structure

permission:
  edit: "deny"           # deny all file edits
  bash: 
    "*": "ask"           # ask before any bash
    "npm test": "allow"  # but allow npm test
    "rm -rf *": "deny"   # never allow rm -rf
  webfetch: "allow"      # allow web fetching
  skill:
    "*": "deny"          # deny all skills by default
    "security-*": "allow" # allow security-prefixed skills

Permission Levels

LevelBehavior
allowExecute without confirmation
askPrompt user before executing
denyBlock entirely

Bash Pattern Matching

Patterns are matched in order of specificity:

  1. Exact match: "npm test": "allow"
  2. Prefix match: "npm *": "ask"
  3. Wildcard: "*": "deny"
permission:
  bash:
    "*": "deny"              # Default deny
    "git *": "allow"         # Allow git commands
    "npm *": "allow"         # Allow npm commands
    "rm *": "ask"            # Ask for rm
    "rm -rf *": "deny"       # MUST NOT allow rm -rf
</rules> <guidelines>

Tools Configuration

Enable or disable specific tools:

tools:
  question: "enabled"    # Force enable question tool
  webfetch: "disabled"   # Disable web fetching
  task: "disabled"       # Prevent delegation

Key Tools

ToolPurpose
questionInteractive Q&A with user (clarification)
delegateAsync background task delegation
taskSync subagent delegation
todowriteTask list management
todoreadRead current task list
skillLoad specialized skills
</guidelines> <examples>

Agent Archetypes

Analyzer (Read-Only)

---
description: Code analysis expert
mode: subagent
temperature: 0.1
permission:
  edit: "deny"
  bash:
    "*": "deny"
    "git log *": "allow"
    "git diff *": "allow"
---

Builder (Full Access)

---
description: Implementation specialist
mode: subagent
model: anthropic/claude-sonnet-4-20250514
temperature: 0.4
---
# No permission block = full access

Researcher (Web + Read)

---
description: Documentation researcher
mode: subagent
temperature: 0.2
permission:
  edit: "deny"
  bash:
    "*": "deny"
---

Specialist (Skill-Based)

---
description: |-
  Security vulnerability scanner. Use for audits and reviews.
mode: subagent
temperature: 0.2
permission:
  edit: "deny"
  bash:
    "*": "deny"
  skill:
    "*": "deny"
    "security-*": "allow"
---

System Prompt Structure

The markdown body becomes the agent's system prompt:

---
description: My agent
mode: primary
---

# Role

You are a [specific role] specializing in [domain].

## Objective

[Clear mission statement]

## Instructions

- MUST [required behavior]
- SHOULD [recommended behavior]
- MAY [optional behavior]
- MUST NOT [prohibited behavior]

## Workflow

1. [First step]
2. [Second step]
3. [Third step]

## Output Format

[Expected output structure]
</examples> <constraints>

Validation

After creating an agent:

opencode run "test"

Then test by routing to it:

  • If primary: Select from agent menu
  • If subagent: Use task tool to invoke
</constraints>
Skills Info
Original Name:opencode-agentsAuthor:justinlevinedotme