zeus-agents

Create and configure specialized AI agents with YAML frontmatter in OpenCode environments.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Aveer/OpenZeus --skill zeus-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zeus-agents
Source: https://github.com/Aveer/OpenZeus/tree/main/skills/zeus-agents
Command: npx skills add https://github.com/Aveer/OpenZeus --skill zeus-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of creating, configuring, and maintaining specialized AI agents within an OpenCode workspace, ensuring consistent behavior and permission management.

Core Features & Use Cases

  • Standardized Agent Creation: Provides a structured workflow and templates for defining agent identity, system prompts, and operational modes.
  • Granular Permission Control: Enables precise definition of tool access, including bash command restrictions and file system permissions.
  • Use Case: Quickly deploy a specialized code reviewer agent that has read-only access to git logs and diffs, or a task-specific builder agent with write permissions for specific project directories.

Quick Start

Use the zeus-agents skill to generate a new subagent configuration file for a security auditor in the current project directory.

Frequently Asked Questions about zeus-agents

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

FAQPage Schema
How do I create custom OpenCode agents with specific system prompts?

To create custom OpenCode agents, you define the agent identity, system prompts, and operational modes using structured YAML frontmatter. This standardizes agent creation and ensures consistent behavior across persistent assistant workflows within your workspace.

Can I restrict bash command permissions for AI agents in an OpenCode environment?

Yes, you can restrict bash command permissions for AI agents in an OpenCode environment. The configuration process enables granular permission control, allowing precise definition of tool access, bash command restrictions, and file system permissions for security.

What is the best way to configure a read-only code reviewer agent in OpenCode?

The best way to configure a read-only code reviewer agent is to use predefined security patterns that limit tool access. You can deploy a specialized agent with read-only access restricted to git logs and diffs through granular permission settings.

How do agent operational modes and YAML frontmatter standardize persistent assistant workflows?

Agent operational modes and YAML frontmatter standardize persistent assistant workflows by providing a structured template for defining agent behavior. This ensures consistent configuration and maintenance of specialized AI agents across different workspace environments.

Do I need predefined security patterns to manage file system permissions for OpenCode agents?

You need predefined security patterns to manage file system permissions for OpenCode agents safely. These patterns ensure consistent agent behavior by enforcing granular permission control, preventing unauthorized write access to project directories.

Why are my specialized AI agents behaving inconsistently across different OpenCode workspace tasks?

Specialized AI agents behave inconsistently across OpenCode workspace tasks without standardized configuration. Applying structured YAML frontmatter and predefined operational modes ensures consistent agent behavior and reliable permission management for persistent workflows.