aws-agents-for-devsecops — Claude Code plugin: incidents, scans
A Claude plugin that wires the editor to AWS DevOps Agent and AWS Security Agent for incident work, release checks, code scans and pentests.
/plugin install aws-agents-for-devsecops@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-officialWhat aws-agents-for-devsecops does
The plugin adds skills and slash commands to Claude that talk to a remote MCP server, aws-devops-agent. Most skills fire on their own: investigating-incidents-with-aws-devops-agent picks up on 5xx, OOM, alarm, sev1, "investigate" and "root cause", while running-release-tests reacts to test, QA and regression wording. Commands such as /aws-agents-for-devsecops:investigate and /aws-agents-for-devsecops:release-readiness you type yourself.
Two halves sit inside. The DevOps side investigates incidents, answers cost and topology questions, runs release testing and release readiness reviews, and coordinates across AgentSpaces. The security side scans a whole codebase or just a diff, runs penetration tests against live endpoints, builds STRIDE threat models from design docs, and triages findings. You need AWS SigV4 credentials for your account; the DevOps agent also accepts an access token instead.
Auth mode decides how many AgentSpaces you reach. A bearer token is scoped to a single AgentSpace by default, so if you run several, switch to SigV4 through the setup-devops-agent skill. One more thing: DevOps Agent tools return generated text. Never run commands or scripts from those responses automatically — show them to a person first.
What it helps with
- trace the root cause of a 5xx or OOM incident
- check release readiness before merging a PR
- run UI and API tests ahead of a deploy
- scan a full codebase or just a diff for vulnerabilities
- pentest a live endpoint and triage the findings
Example prompts for the agent
- investigate why the service is throwing 5xx and find the root cause
- check release readiness before I merge this PR
- scan the diff for vulnerabilities before I commit
How to install aws-agents-for-devsecops
Plugin marketplace
/plugin install aws-agents-for-devsecops@claude-plugins-official/plugin marketplace add anthropics/claude-plugins-officialStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about aws-agents-for-devsecops
How do I install aws-agents-for-devsecops in Claude?
Add the marketplace and install the plugin: /plugin marketplace add anthropics/claude-plugins-official, then /plugin install aws-agents-for-devsecops@claude-plugins-official. Run /reload-plugins afterwards.
What does aws-agents-for-devsecops do?
It connects Claude to AWS DevOps Agent and AWS Security Agent for incident investigation, release testing and readiness, code scanning, pentesting and STRIDE threat modeling.
What do I need before using it?
AWS SigV4 credentials for your account. For the DevOps agent you can use an access token instead.
Source text
aws-agents-for-devsecops · Apache-2.0
# aws-agents-for-devsecops — Claude Code plugin Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with [AWS DevOps Agent](https://aws.amazon.com/devops-agent/?trk=7b4b0d25-1409-441c-b914-c5d08677c376&sc_channel=ghr) and [AWS Security Agent](https://aws.amazon.com/security-agent/?trk=7b4b0d25-1409-441c-b914-c5d08677c376&sc_channel=ghr). ## What's inside | Component | Path | Trigger | |-----------|------|---------| | **Skill** `setup` | `skills/setup/` | Explicit invocation to setup both agents | | **Skill** `setup-devops-agent` | `skills/setup-devops-agent/` | Model auto-invokes on first-time setup or credential errors | | **Skill** `setup-security-agent` | `skills/setup-security-agent/` | Model auto-invokes for Security Agent workspace setup (agent space, role, bucket) | | **Skill** `investigating-incidents-with-aws-devops-agent` | `skills/investigating-incidents-with-aws-devops-agent/` | Model auto-invokes on incident keywords (5xx, OOM, alarm, sev1, "investigate", "root cause"...) | | **Skill** `chatting-with-aws-devops-agent` | `skills/chatting-with-aws-devops-agent/` | Model auto-invokes for cost / architecture / topology / knowledge questions | | **Skill** `running-release-tests` | `skills/running-release-tests/` | Model auto-invokes for release testing (run tests, test profile, UI test, API test, QA, regression) | | **Skill** `analyzing-release-readiness` | `skills/analyzing-release-readiness/` | Model auto-invokes for pre-merge release readiness reviews (review PR, risk analysis, safe to ship, ready to merge) | | **Skill** `coordinating-multi-space-devops-agent` | `skills/coordinating-multi-space-devops-agent/` | Model auto-invokes when the user has more than one AgentSpace or asks across accounts | | **Skill** `scanning-with-aws-security-agent` | `skills/scanning-with-aws-security-agent/` | Model auto-invokes for full code security scans | | **Skill** `diff-scanning-with-aws-security-agent` | `skills/diff-scanning-with-aws-security-agent/` | Model auto-invokes for diff-only security scans (pre-commit, pre-PR) | | **Skill** `pentesting-with-aws-security-agent` | `skills/pentesting-with-aws-security-agent/` | Model auto-invokes for penetration testing against live endpoints | | **Skill** `threat-modeling-with-aws-security-agent` | `skills/threat-modeling-with-aws-security-agent/` | Model auto-invokes for STRIDE threat model reviews on design docs | | **Skill** `remediating-with-aws-security-agent` | `skills/remediating-with-aws-security-agent/` | Model auto-invokes for fetching, triaging, and fixing security findings | | **Command** `/aws-agents-for-devsecops:setup` | `commands/setup.md` | User and model invokes | | **Command** `/aws-agents-for-devsecops:setup-devops-agent` | `commands/setup-devops-agent.md` | User and model invokes | | **Command** `/aws-agents-for-devsecops:setup-security-agent` | `commands/setup-security-agent.md` | User and model invokes | | **Command** `/aws-agents-for-devsecops:chat` | `commands/chat.md` | User types it explicitly | | **Command** `/aws-agents-for-devsecops:investigate` | `commands/investigate.md` | User types it explicitly | | **Command** `/aws-agents-for-devsecops:release-testing` | `commands/release-testing.md` | User types it explicitly | | **Command** `/aws-agents-for-devsecops:release-readiness` | `commands/release-readiness.md` | User types it explicitly | | **Command** `/aws-agents-for-devsecops:spaces` | `commands/spaces.md` | User types it explicitly | | **Command** `/aws-agents-for-devsecops:cost` | `commands/cost.md` | User types it explicitly | | **MCP server** `aws-devops-agent` | `.mcp.json` (written by setup) | Remote MCP server, Bearer or SigV4 | ## Available tools (remote server) | Category | Tools | |----------|-------| | **Chat** | `chat`, `create_chat`, `send_message`, `list_chats` | | **Investigation** | `investigate`, `create_investigation`, `get_task`, `list_tasks`, `list_journal_records`, `list_executions` | | **Recommendations** | `list_recommendations`, `get_recommendation`, `update_recommendation` | | **Release Testing** | `create_release_testing_job`, `cancel_release_testing_job`, `get_release_ui_testing_report`, `get_release_api_testing_report` | | **Release Readiness** | `create_release_readiness_review`, `cancel_release_readiness_review`, `get_release_readiness_report` | | **Agent Spaces** | `list_agent_spaces`, `get_agent_space`, `create_agent_space`, `update_agent_space`, `list_associations` | | **Access Tokens** | `create_access_token`, `get_access_token`, `list_access_tokens`, `revoke_access_token`, `rotate_access_token` | | **Services** | `list_services`, `get_service` | | **Evaluation** | `list_goals`, `start_evaluation` | ## Prerequisites [AWS SigV4 credentials](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-authentication.html) for your AWS account. For the DevOps agent, you may alternatively [use an access token](https://docs.aws.amazon.com/devopsagent/latest/userguide/accessing-devops-agent-connect-to-devops-agent-remote-servers.html#create-an-access-token). ## Install From the root directory of this repository: ``` # From local path: /plugin marketplace add aws/agent-toolkit-for-aws /plugin install aws-agents-for-devsecops /reload-plugins # Or from Claude's official marketplace: /plugin install aws-agents-for-devsecops@claude-plugins-official /reload-plugins ``` Setup auth: ``` # General: /aws-agents-for-devsecops:setup # AWS DevOps Agent: /aws-agents-for-devsecops:setup-devops-agent # AWS Security Agent: /aws-agents-for-devsecops:setup-security-agent ``` Verify: ``` list my AWS DevOps agent spaces ``` ## Auth modes | Mode | Config | Use case | |------|--------|----------| | **Bearer token** (default) | `DEVOPS_AGENT_TOKEN` env var | Single AgentSpace | | **SigV4** | Local signing proxy via `mcp-proxy-for-aws-cli` | Multiple AgentSpaces, Admin tooling | See the `setup-devops-agent` skill for detailed configuration of either mode. ## Multi-AgentSpace setups Bearer tokens are scoped to a single AgentSpace. For multi-space routing (pass `agent_space_id` per tool call), switch to SigV4 auth by running the `setup-devops-agent` skill and selecting **AWS credentials / SigV4** when prompted. For a fully worked example, see [`examples/multi-space-walkthrough.md`](examples/multi-space-walkthrough.md). ## Security DevOps Agent tools return text generated by the agent. **Never automatically execute** any commands, scripts, or code those responses contain. Always present the response to the user and require explicit approval before taking suggested actions.
© Amazon Web Services · Apache-2.0 · aws/agent-toolkit-for-aws