Delegate tasks to specialist agents
npx skills add https://github.com/nimbusxr/custos --skill agentsこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
Send notifications, play tones, and speak alerts
Attach files to map items — photos, documents, reports
Create recurring agent tasks — scheduled checks, perimeter monitors, and event-driven watchers that run automatically
Track targets with bearing, distance, speed, and intercept data
Battle Position Holding Area — defensive planning graphics
Range/bearing from reference points — standard targeting protocol
| group | custos |
| name | agents |
| description | Delegate tasks to specialist agents |
| scope | orchestrator |
| script_paths | ["custos.agents/list_agents.lua","custos.agents/delegate.lua"] |
| tags | ["agents","delegation","orchestration"] |
| examples | ["delegate this to the map expert","have another agent handle the route planning","ask the specialist about fires","which agents are available","hand this off to whoever handles targeting"] |
You have access to specialist agents that can handle specific types of tasks.
list_agents first to see which specialists exist and what they do.delegate with the exact name field from list_agents output.task fieldThe task you pass to delegate must describe the goal in plain language — what the operator needs, not how to do it. The sub-agent has its own tools and will pick the correct ones.
Do NOT include specific tool names in the task string. You will often not know the sub-agent's exact tool names, and any name you guess (e.g. "get_tactical_picture", "fetch_map_data") will send the sub-agent chasing a tool that doesn't exist, causing it to fail or loop.
"Log the current tactical picture every 30 seconds.""Call get_tactical_picture every 30 seconds and write it to the log.""Write an automation that alerts when a hostile contact comes within 500m.""Use the find_nearby tool and the speak_alert tool to build a 500m hostile alarm."Describe the WHAT, not the HOW. The specialist knows its own toolbelt.