agentic-subagents

Create and manage OpenCode subagents with frontmatter and permissions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/moonpixels/laravel-skeleton-react --skill agentic-subagents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-subagents
Source: https://github.com/moonpixels/laravel-skeleton-react/tree/main/.opencode/skills/agentic-subagents
Command: npx skills add https://github.com/moonpixels/laravel-skeleton-react --skill agentic-subagents

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenCode subagents provide a standardized, governed way to route automation tasks and enforce safety constraints across projects by encapsulating workflows as discrete, permissioned units.

Core Features & Use Cases

  • Define subagents under .opencode/agents with a clear frontmatter contract (description, mode, temperature, steps, permissions) to enable auto-routing and delegation.
  • Enforce safety and scope with a dedicated permission model and step controls to prevent unauthorized actions.
  • Reuse proven patterns and references to rapidly compose multi-step automation tasks such as code reviews, tests, and security checks.

Quick Start

Create a new subagent file under .opencode/agents/ using the described frontmatter and routing guidance.

Frequently Asked Questions about agentic-subagents

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

FAQPage Schema
How do I automate safe routing with OpenCode subagents?

Automate safe routing by defining subagents under .opencode/agents with frontmatter specifying name, description, mode, temperature, steps, and permissions to enforce governance and scope controls.

What frontmatter is required to create an OpenCode subagent?

Required frontmatter for an OpenCode subagent includes name, description, mode, temperature, steps, and permission. Optional fields like skills, references, and assets can further structure guidance and policies.

How does the permission model prevent unauthorized actions in subagent workflows?

The permission model enforces safety by applying dedicated scope controls and step boundaries to subagents, preventing unauthorized actions during automatic routing and multi-step automation tasks.

Can I reuse templates and references to compose multi-step automation tasks?

Yes, you can reuse proven patterns and references to rapidly compose multi-step automation tasks such as code reviews, tests, and security checks across governed subagents.

Does this approach support auto-routing and delegation for security checks?

Yes, defining subagents with a clear frontmatter contract under .opencode/agents enables automatic routing and delegation for governed tasks including security checks and code reviews.

What are the limitations of governing workflows with subagent step controls?

Step controls limit subagent actions to predefined boundaries to prevent unauthorized actions, meaning any workflow exceeding the defined permission scope or steps configuration will be restricted from execution.