investigate

investigate is a command for coding agents from aws/agent-toolkit-for-aws. It costs 16 tokens per session (274 once invoked), scanned A, original, Apache-2.0.

A command that starts a deep investigation into the underlying cause of an incident using an AWS DevOps Agent. It gathers project context, streams progress, and reports findings and suggested mitigations.

In plain words
What is it for?
Investigating errors or outages using recent commits, dependency files, infrastructure configuration, and logs, then reviewing recommended fixes without applying them automatically.
Why use it?
It organizes the investigation and keeps the user informed while the external agent examines the incident.

Command

Part of the aws-agents-for-devsecops plugin — 13 skills, 9 commands, 1 MCP server shipped together

About the project

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.

aws/agent-toolkit-for-aws · 2,533 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/aws/agent-toolkit-for-aws/investigate
Clone the repo
git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws

Or install aws-agents-for-devsecops, the plugin that ships this one along with the rest of its 13 skills, 9 commands, 1 MCP server.

Wrote 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.

agentmods badge for investigate

README.md
[![agentmods](https://agentmods.dev/badge/commands/aws/agent-toolkit-for-aws/investigate.svg)](https://agentmods.dev/commands/aws/agent-toolkit-for-aws/investigate)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 274 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00274
Opus 5 $0.00008 $0.00137
Sonnet 5 $0.00003 $0.00055
Haiku 4.5 $0.00002 $0.00027

Measured 6d ago against content hash 9b9b1d2b0e9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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 6d 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.

plugins/aws-agents-for-devsecops/commands/investigate.md · 16 lines

What it actually says

Use the investigating-incidents-with-aws-devops-agent skill workflow.

  1. Gather local context — git log --oneline -10, dependency manifest, relevant IaC, the error/log the user is looking at.
  2. Call aws_devops_agent__investigate(title="$ARGUMENTS — <local context summary>").
  3. Tell the user investigations take 5–8 minutes and that you'll keep them posted.
  4. Poll aws_devops_agent__get_task(task_id="TASK_ID") every 30–45s.
  5. 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 the investigating-incidents-with-aws-devops-agent skill.
  6. On COMPLETED: pull final findings, then call aws_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.

Changes

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.

  1. 6d ago First seen · 16 lines · 16 tokens per session scan A 9b9b1d2b0e9a

Subscribe to this mod's changes

investigate is a command published in the GitHub repository aws/agent-toolkit-for-aws (2,533 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. 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.