agentic-commands

Create and manage OpenCode command templates with frontmatter and token placeholders.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Write OpenCode command templates that agents can execute reliably in TUI or headless mode. This helps teams automate repetitive agent workflows without manual scripting.

Core Features & Use Cases

  • Store commands in .opencode/commands/{name}.md (global: ~/.config/opencode/commands/{name}.md).
  • Use $ARGUMENTS (or $1, $2) for user input, !`cmd` for shell output, and @file to include file contents.
  • Write explicit success/failure handling and verification steps.
  • Avoid destructive commands unless explicitly asked; require confirmation when needed.
  • Prefer subtask: true for noisy or multi-step workflows.

Quick Start

Create a new command template at .opencode/commands/{name}.md and define its behavior.

Frequently Asked Questions about agentic-commands

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

FAQPage Schema
How do I create OpenCode command templates for agent automation?

Create OpenCode command templates by defining a markdown file at `.opencode/commands/{name}.md` with frontmatter-driven structure to automate agent workflows reliably in TUI or headless mode.

What tokens and placeholders are supported in OpenCode command templates?

OpenCode command templates support `$ARGUMENTS` or `$1` and `$2` for user input, ``!`cmd` `` for shell output, and `@file` to include file contents directly within your template definitions.

Can I use OpenCode command templates in headless environments?

Yes, OpenCode command templates execute reliably in both TUI and headless environments, allowing teams to automate repetitive agent workflows without manual scripting across different modes.

How do I handle success and failure states in OpenCode command templates?

Write explicit success and failure handling along with verification steps directly in your OpenCode command templates, and prefer `subtask: true` for noisy or multi-step workflows.

Where are OpenCode command templates stored for global access?

Store OpenCode command templates globally at `~/.config/opencode/commands/{name}.md` or locally within your project at `.opencode/commands/{name}.md` for scoped automation workflows.

Can OpenCode command templates run destructive shell commands?

OpenCode command templates avoid destructive commands unless explicitly asked, requiring confirmation when needed to ensure safe execution of automated agent workflows.