🙏 This repository is forked from wshobson/agents, the original creator of this comprehensive subagent collection. Thank you for building this amazing resource for the AI coding assistant community!
A comprehensive collection of specialized AI agents for both Claude Code and OpenCode, providing domain-specific expertise across software development, infrastructure, and business operations.
This repository provides production-ready agents that extend AI coding assistants' capabilities with specialized knowledge. The collection includes:
- 81 Claude Code agents - Optimized for Claude's subagent system
- 81 OpenCode skills - Mirrored from the Claude collection in OpenCode format
Each agent incorporates:
- Current industry best practices and standards (2024/2025)
- Production-ready patterns and enterprise architectures
- Deep domain expertise with 8-12 capability areas per agent
- Modern technology stacks and frameworks
- Optimized model selection based on task complexity
agents/
├── claude/ # Claude Code agents (flat files, e.g. claude/python-pro.md)
├── opencode/ # OpenCode skills (per-skill dirs, e.g. opencode/python-pro/SKILL.md)
├── scripts/ # Conversion, linting, and utility scripts
├── docs/ # Usage and migration docs
├── CLAUDE.md # Claude Code specific documentation
├── OPENCODE.md # OpenCode specific documentation
└── README.md # This file
- Claude Code agents: See CLAUDE.md for setup and usage
- OpenCode agents: See OPENCODE.md for setup and usage
Claude agents live as flat markdown files in claude/.
Quick examples:
claude/code-reviewer.mdclaude/security-auditor.mdclaude/python-pro.mdclaude/cloud-architect.md
To list all available Claude agents:
ls claude/*.mdClaude agents specify model choice in each file's frontmatter (haiku, sonnet, opus, or provider-specific model IDs). Model assignment is based on task complexity and expected reasoning depth.
To inspect model usage in the current repo:
rg '^model:' claude/*.mdOpenCode skills are organized as one directory per skill under opencode/, each with a SKILL.md file. The current repository mirrors 81 skills from the Claude set.
Quick examples:
opencode/code-reviewer/SKILL.mdopencode/security-auditor/SKILL.mdopencode/python-pro/SKILL.mdopencode/cloud-architect/SKILL.md
To list all available OpenCode skills:
ls opencode/*/SKILL.md- Open-source focused: Prioritizes FOSS tools and libraries
- Privacy by default: Local-first processing and data minimization
- Transparent operation: Includes reasoning traces and decision explanations
- Community oriented: Supports collaborative development patterns
- Self-hostable: Designed for on-premise and air-gapped deployments
Note: Claude Code expects agents directly in ~/.claude/agents/, not in subdirectories. See INSTALLATION.md for detailed setup options.
Quick setup with symlink:
git clone https://github.com/brianluby/agents.git ~/agents-repo
ln -s ~/agents-repo/claude ~/.claude/agents# Clone the repository
git clone https://github.com/brianluby/agents.git
# Link OpenCode agents globally
ln -s /path/to/agents/opencode/* ~/.config/opencode/agent/
# Or link to a project
ln -s /path/to/agents/opencode/* .opencode/agent/See OPENCODE.md for detailed OpenCode setup instructions.
Validate agent metadata before committing:
python scripts/lint_agents.py --roots opencode claude --require-modelAuto-fill missing model values:
python3 scripts/lint_agents.py --roots opencode --fix-missing-model zai/glm-4.6Auto-fix canonical key ordering & validate allowed tools:
python scripts/lint_agents.py --roots opencode claude --check-order --require-modelSoft (non-failing) report mode:
python scripts/lint_agents.py --roots opencode --require-model --warn-onlyInstall pre-commit hook:
ln -s ../../.githooks/agent-lint .git/hooks/pre-commitSee CHANGELOG.md for normalization history.
The repo ships lightweight tool scripts (under scripts/tools/) used by some OpenCode agents or local workflows:
glob_tool.py– Glob file listing (no content read)grep_tool.py– Regex line search with match cap (default 500)diff_tool.py– Unified diff (file↔file / dir↔dir) with byte limitformat_tool.py– Minimal trailing-space + final newline normalizer (dry-run by default)webfetch_tool.py– Disabled-by-default HTTP(S) fetch (text-only, 100 KB cap, requires--alloworOPENCODE_ALLOW_WEB=1)
List allowed agent tool names:
python scripts/lint_agents.py --list-toolsEnable only what an agent strictly needs; omit webfetch unless remote context is essential.
Claude Code automatically selects the appropriate subagent based on task context and requirements. The system analyzes your request and delegates to the most suitable specialist.
Specify a subagent by name to use a particular specialist:
"Use code-reviewer to analyze the recent changes"
"Have security-auditor scan for vulnerabilities"
"Get performance-engineer to optimize this bottleneck"
code-reviewer: Analyze component for best practices
security-auditor: Check for OWASP compliance
tdd-orchestrator: Implement feature with test-first approach
performance-engineer: Profile and optimize bottlenecks
backend-architect: Design authentication API
frontend-developer: Create responsive dashboard
graphql-architect: Design federated GraphQL schema
mobile-developer: Build cross-platform mobile app
devops-troubleshooter: Analyze production logs
cloud-architect: Design scalable AWS architecture
network-engineer: Debug SSL certificate issues
database-admin: Configure backup and replication
terraform-specialist: Write infrastructure modules
data-scientist: Analyze customer behavior dataset
ai-engineer: Build RAG system for document search
mlops-engineer: Set up experiment tracking
ml-engineer: Deploy model to production
business-analyst: Create metrics dashboard
documentation-expert: Generate technical documentation
api-documenter: Write OpenAPI specifications
content-marketer: Create SEO-optimized content
Subagents coordinate automatically for complex tasks. The system intelligently sequences multiple specialists based on task requirements.
Feature Development
"Implement user authentication"
→ backend-architect → frontend-developer → test-automator → security-auditor
Performance Optimization
"Optimize checkout process"
→ performance-engineer → database-optimizer → frontend-developer
Production Incidents
"Debug high memory usage"
→ incident-responder → devops-troubleshooter → debugger → performance-engineer
Infrastructure Setup
"Set up disaster recovery"
→ database-admin → database-optimizer → terraform-specialist
ML Pipeline Development
"Build ML pipeline with monitoring"
→ mlops-engineer → ml-engineer → data-engineer → performance-engineer
For sophisticated multi-agent orchestration, use the Claude Code Commands collection which provides 52 pre-built slash commands:
/full-stack-feature # Coordinates 8+ agents for complete feature development
/incident-response # Activates incident management workflow
/ml-pipeline # Sets up end-to-end ML infrastructure
/security-hardening # Implements security best practices across stack
Each subagent is defined as a Markdown file with frontmatter:
---
name: subagent-name
description: Activation criteria for this subagent
model: haiku|sonnet|opus # Optional: Model selection
tools: tool1, tool2 # Optional: Tool restrictions
---
System prompt defining the subagent's expertise and behavior- haiku: Simple, deterministic tasks with minimal reasoning
- sonnet: Standard development and engineering tasks
- opus: Complex analysis, architecture, and critical operations
Agents execute in sequence, passing context forward:
backend-architect → frontend-developer → test-automator → security-auditor
Multiple agents work simultaneously on different aspects:
performance-engineer + database-optimizer → Merged analysis
Dynamic agent selection based on analysis:
debugger → [backend-architect | frontend-developer | devops-troubleshooter]
Primary work followed by specialized review:
payment-integration → security-auditor → Validated implementation
| Task | Recommended Agent | Key Capabilities |
|---|---|---|
| API Design | backend-architect |
RESTful APIs, microservices, database schemas |
| Cloud Infrastructure | cloud-architect |
AWS/Azure/GCP design, scalability planning |
| UI/UX Design | ui-ux-designer |
Interface design, wireframes, design systems |
| System Architecture | architect-review |
Pattern validation, consistency analysis |
| Language Category | Agents | Primary Use Cases |
|---|---|---|
| Systems Programming | c-pro, cpp-pro, rust-pro, golang-pro |
OS interfaces, embedded systems, high performance |
| Web Development | javascript-pro, typescript-pro, python-pro, ruby-pro, php-pro |
Full-stack web applications, APIs, scripting |
| Web Frameworks | django-pro, fastapi-pro |
Django and FastAPI development |
| Enterprise | java-pro, csharp-pro, scala-pro |
Large-scale applications, enterprise systems |
| Mobile | ios-developer, flutter-expert, mobile-developer |
Native and cross-platform mobile apps |
| Specialized | elixir-pro, unity-developer, minecraft-bukkit-pro |
Domain-specific development |
| Task | Recommended Agent | Key Capabilities |
|---|---|---|
| Production Issues | devops-troubleshooter |
Log analysis, deployment debugging |
| Critical Incidents | incident-responder |
Outage response, immediate mitigation |
| Database Performance | database-optimizer |
Query optimization, indexing strategies |
| Database Operations | database-admin |
Backup, replication, disaster recovery |
| Infrastructure as Code | terraform-specialist |
Terraform modules, state management |
| Network Issues | network-engineer |
Network debugging, load balancing |
| Kubernetes | kubernetes-engineer |
K8s configurations, cluster management |
| Platform Engineering | platform-engineer |
Internal developer platforms, service mesh |
| Site Reliability | sre-engineer |
SLIs/SLOs, error budgets, reliability practices |
| Task | Recommended Agent | Key Capabilities |
|---|---|---|
| Code Review | code-reviewer |
Security focus, best practices |
| Security Audit | security-auditor |
Vulnerability scanning, OWASP compliance |
| Test Creation | test-automator |
Unit, integration, E2E test suites |
| Performance Issues | performance-engineer |
Profiling, optimization |
| Bug Investigation | debugger |
Error resolution, root cause analysis |
| QA Engineering | qa-engineer |
Manual testing strategies, test plans |
| Config Security | config-security-auditor |
Configuration security, secrets management |
| Supply Chain Security | supply-chain-security |
Dependency scanning, SBOM generation |
| Task | Recommended Agent | Key Capabilities |
|---|---|---|
| Data Analysis | data-scientist |
SQL queries, statistical analysis |
| LLM Applications | ai-engineer |
RAG systems, prompt pipelines |
| ML Development | ml-engineer |
Model training, feature engineering |
| ML Operations | mlops-engineer |
ML infrastructure, experiment tracking |
- Automatic selection - Let Claude Code analyze context and select optimal agents
- Clear requirements - Specify constraints, tech stack, and quality standards
- Trust specialization - Each agent is optimized for their specific domain
- High-level requests - Allow agents to coordinate complex multi-step tasks
- Context preservation - Ensure agents have necessary background information
- Integration review - Verify how different agents' outputs work together
- Direct invocation - Specify agents when you need particular expertise
- Strategic combination - Use multiple specialists for validation
- Review patterns - Request specific review workflows (e.g., "security-auditor reviews API design")
- Monitor effectiveness - Track which agents work best for your use cases
- Iterative refinement - Use agent feedback to improve requirements
- Complexity matching - Align task complexity with agent capabilities
To add a new subagent:
- Create a new
.mdfile with appropriate frontmatter - Use lowercase, hyphen-separated naming convention
- Write clear activation criteria in the description
- Define comprehensive system prompt with expertise areas
- Ensure request clearly indicates the domain
- Be specific about task type and requirements
- Use explicit invocation if automatic selection fails
- Provide more context about tech stack
- Include specific requirements in request
- Use direct agent naming for precise control
- Normal behavior - specialists have different priorities
- Request reconciliation between specific agents
- Consider trade-offs based on project requirements
- Include background information in requests
- Reference previous work or patterns
- Provide project-specific constraints
MIT License - see LICENSE file for details.
