emasoft/amcos-agent-spawning
skills/amcos-agent-spawning/SKILL.md
Use when creating new agents. Trigger with agent spawn requests, pre-flight validation, or new agent creation. Loaded by ai-maestro-chief-of-staff-main-agent
data-ai
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add emasoft/ai-maestro-chief-of-staff amcos-agent-spawningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 4:28 AM82.7s10 files scanned
SKILL.md
- name:
- amcos-agent-spawning
- description:
- Use when creating new agents. Trigger with agent spawn requests, pre-flight validation, or new agent creation. Loaded by ai-maestro-chief-of-staff-main-agent
- user-invocable:
- false
- license:
- Apache-2.0
- compatibility:
- Requires AI Maestro installed.
- author:
- Emasoft
- version:
- 1.0.0
- context:
- fork
- agent:
- ai-maestro-chief-of-staff-main-agent
Agent Spawning
Overview
Creates new agent instances with OAuth validation, plugin setup, and registry registration.
Prerequisites
- AI Maestro running,
ai-maestro-agents-managementandagent-messagingskills available - tmux installed, team registry accessible via REST API (
GET /api/teams)
Instructions
Copy this checklist and track your progress:
- [ ] Request GovernanceRequest approval from sourceManager via amcos-permission-management
- [ ] Validate OAuth scopes (repo, project, read:project)
- [ ] Select agent type and unique session name
- [ ] Setup plugin from cache to agent directory
- [ ] Create agent instance via ai-maestro-agents-management skill
- [ ] Verify agent online and register in team registry
- [ ] Send welcome message via agent-messaging skill
Pre-Flight: Validate OAuth Scopes
gh auth status 2>&1 | grep -q "project" || echo "ERROR: Missing project scope"
Required: repo, project, read:project. If missing, request human to run gh auth refresh -h github.com -s project,read:project. Do NOT proceed if scopes are missing.
Spawn Procedure (PROCEDURE 1)
- Request GovernanceRequest approval - Submit spawn request to sourceManager via
amcos-permission-managementskill. BLOCK until approved. - Select agent type from roles (Orchestrator, Architect, Integrator, Programmer)
- Choose session name - Format:
<role-prefix>-<project>-<descriptive>(must be unique) - Setup plugin - Copy from
$HOME/.claude/plugins/cache/ai-maestro/<plugin>/<latest>/to$HOME/agents/<session>/.claude/plugins/<plugin>/ - Create instance via
ai-maestro-agents-managementskill with args:--dangerously-skip-permissions --chrome --add-dir /tmp --plugin-dir <path> --agent <agent-name> - Verify agent appears online in agent list
- Register via
uv run python scripts/amcos_team_registry.py add-agent - Send welcome message via
agent-messagingskill
The --agent Flag
| Role | --agent Flag Value |
|------|--------------------|
| Orchestrator | ai-maestro-orchestrator-main-agent |
| Architect | ai-maestro-architect-main-agent |
| Integrator | ai-maestro-integrator-main-agent |
| Programmer | ai-maestro-programmer-main-agent |
Output
| Step | Expected Output | |------|----------------| | Pre-flight | OAuth scopes confirmed | | Spawn | tmux session created, agent running | | Registry | Agent registered as "running" |
Error Handling
| Issue | Resolution |
|-------|-----------|
| OAuth scopes missing | Block spawn, request human gh auth refresh |
| Plugin validation failed | Verify cache exists at source path |
| Session name collision | Choose different unique name |
| Resource limit exceeded | Queue request, hibernate oldest idle |
Examples
Spawn a Programmer Agent
# 1. Verify scopes
gh auth status 2>&1 | grep -q "project" && echo "OK"
# 2. Copy plugin
cp -r ~/.claude/plugins/cache/ai-maestro/ai-maestro-programmer-agent/latest/* \
~/agents/ampa-svgbbox-impl/.claude/plugins/ai-maestro-programmer-agent/
# 3. Create via ai-maestro-agents-management skill:
# Name: ampa-svgbbox-impl, Dir: ~/agents/ampa-svgbbox-impl/
# Args: --agent ai-maestro-programmer-main-agent
# 4. Register + send welcome message
Checklist
Copy this checklist and track your progress:
- [ ] Validate OAuth scopes (repo, project, read:project)
- [ ] Request GovernanceRequest approval
- [ ] Create agent via ai-maestro-agents-management skill
- [ ] Register in team registry and send welcome message
Resources
Related Skills
emasoft/amcos-context-management
data-ai
VerifiedTrustedCommunity
Use when managing context or patterns. Trigger with context update or compaction needs. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026
emasoft/amcos-context-management-ref
data-ai
VerifiedTrustedCommunity
Use when consulting detailed context management references. Trigger with context management lookups. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026
emasoft/amcos-config-snapshot
data-ai
VerifiedTrustedCommunity
Use when capturing config snapshots, detecting config changes, or resolving config version conflicts. Trigger with config management or snapshot needs. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026
emasoft/amcos-config-snapshot-ref
data-ai
VerifiedTrustedCommunity
Use when consulting detailed config snapshot references. Trigger with config snapshot lookups. Loaded by ai-maestro-chief-of-staff-main-agent
SKILL.mdUpdated Apr 26, 2026