Agent Toolkit for AWS is a collection of AWS-supported MCP servers, skills, plugins, commands, and hooks that help AI coding agents build, deploy, and manage applications on AWS. It is used by developers working with AWS services through agents such as Claude Code, Codex, Cursor, and Kiro. The catalogue entries are the toolkit's own agent extensions for AWS development and operations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/aws/agent-toolkit-for-awsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/aws/agent-toolkit-for-aws/investigate)<a href="https://agentmods.dev/commands/aws/agent-toolkit-for-aws/investigate"><img src="https://agentmods.dev/badge/commands/aws/agent-toolkit-for-aws/investigate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/aws/agent-toolkit-for-aws/investigate"><img src="https://agentmods.dev/badge/commands/aws/agent-toolkit-for-aws/investigate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.00274 |
| Opus 5.5 | $0.00006 | $0.00110 |
| Sonnet 5.5 | $0.00003 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
investigate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Use the investigating-incidents-with-aws-devops-agent skill workflow.
- Gather local context —
git log --oneline -10, dependency manifest, relevant IaC, the error/log the user is looking at. - Call
aws_devops_agent__investigate(title="$ARGUMENTS — <local context summary>"). - Tell the user investigations take 5–8 minutes and that you'll keep them posted.
- Poll
aws_devops_agent__get_task(task_id="TASK_ID")every 30–45s. - When
IN_PROGRESS, fetch findings:aws_devops_agent__list_journal_records(execution_id="EXEC_ID", order="ASC"). Summarize each new record using emoji prefixes from theinvestigating-incidents-with-aws-devops-agentskill. - On
COMPLETED: pull final findings, then callaws_devops_agent__list_recommendations(task_id="TASK_ID")for mitigations. Show the user the proposed fix — do not auto-apply.
If $ARGUMENTS is empty, ask the user for a one-line incident description first.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 16 lines · 16 tokens per session scan A 9b9b1d2b0e9a
investigate is a command published in the GitHub repository aws/agent-toolkit-for-aws (2,919 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 274 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
status
Check overall system health and status.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workflows:debug
Interactive debugging for failing workflow instances. Use when user reports workflow errors, instances stuck, or deployment failures.
cloud-run-debug
Diagnose a failing Cloud Run service — Antigravity (agy/Gemini) digests the error logs cheaply, Claude infers the root cause and proposes a fix. Read-only by default; --apply writes the fix to a branch.
analyze
Quick analysis of must-gather data - runs all analysis scripts and provides comprehensive cluster diagnostics.