# Coordinating Multi Space Devops Agent

Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code...

- Repository: https://github.com/aws/agent-toolkit-for-aws (3366 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -g -a claude-code -y`
Codex: `npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -g -a codex -y`
Cursor: `npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -g -a cursor -y`
Gemini CLI: `npx skills add aws/agent-toolkit-for-aws --skill coordinating-multi-space-devops-agent -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add aws/agent-toolkit-for-aws`

## Description

Coordinate the AWS DevOps Agent across multiple AgentSpaces from one Claude Code session, route questions to the right space (prod vs staging vs knowledge), query several spaces in parallel and synthesize, or compare findings across accounts. Use whenever the user has more than one AgentSpace configured, mentions multiple AWS accounts, or asks something like "check both prod and staging", "compare across accounts", or "ask the knowledge space".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Querying multiple AgentSpaces

## Pre-flight

If `aws_devops_agent__list_agent_spaces` is **not** in your available tools, the remote MCP server is not connected. Tell the user to ask "help me set up the AWS DevOps Agent" so the `setup-devops-agent` skill auto-loads.

## Prerequisite: SigV4 auth required

Multi-space routing requires **SigV4 authentication**, Bearer tokens are scoped to a single AgentSpace and cannot route to other spaces.

Many real teams run **more than one AgentSpace**, typically a production space, a staging space, and a dedicated "knowledge" space that holds runbooks shared across accounts. Each space has its own set of associated AWS accounts, runbooks, and history.

This skill is the routing brain. Use it when the user has multiple spaces configured, or when a question genuinely spans accounts.

## Discovering spaces

```
aws_devops_agent__list_agent_spaces()
→ {"agentSpaces": [{"agentSpaceId": "as-abc123", "name": "prod"}, ...]}
```

If only one space is returned, this skill doesn't apply, use `chatting-with-aws-devops-agent` or `investigating-incidents-with-aws-devops-agent` directly (no `agent_space_id` needed).

If more than one is returned, decide whether the user's question is:

| Question shape | Strategy |
|---------------|----------|
| Scoped to one environment ("prod is broken") | Single space, pick the matching one |
| Spans environments ("compare prod vs staging") | **Parallel**, query each, synthesize |
| Generic knowledge ("what runbooks do we have for ECS?") | Route to the **knowledge** space if one is named that way |
| Ambiguous ("our service is slow") | **Ask the user** which environment, don't guess |

## Per-session routing memory

If the user has a routing guide stored locally (e.g. `.claude/aws-agents-for-devsecops.md`, `AGENTS.md`, or per-project notes), read it once at the start of the session and use it as the routing table for the rest of the conversation. Format expected:

The rest: https://github.com/aws/agent-toolkit-for-aws/blob/HEAD/plugins/aws-agents-for-devsecops/skills/coordinating-multi-space-devops-agent/SKILL.md