chat

A command for opening a question-and-answer session with the AWS DevOps Agent. It adds useful local project context, such as infrastructure files, dependency lists, and recent commits, to the question.

In plain words
What is it for?
It helps ask the AWS DevOps Agent about a project, infrastructure, or deployment issue, and send additional questions using the existing conversation.
Why use it?
It saves developers from manually collecting and pasting relevant project details before asking for help. Follow-up questions can continue in the same session.

Command

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/chat
Clone the repo
git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 156 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 $0.00014 $0.00156
Opus 5 $0.00007 $0.00078
Sonnet 5 $0.00003 $0.00031
Haiku 4.5 $0.00001 $0.00016

Measured 3d ago against content hash a95572e942c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

chat 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 3d 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/chat.md · 14 lines

What it actually says

Use the chatting-with-aws-devops-agent skill workflow.

  1. Gather any obviously relevant local context (IaC, dependency manifest, recent git commits) and inject it alongside the question.
  2. Call aws_devops_agent__chat(message="[Local Context]\n<context>\n\n[Question]\n$ARGUMENTS").
  3. Show the response to the user.
  4. If the user wants follow-ups, use aws_devops_agent__send_message(execution_id="<from chat response>", content="<follow-up>").

If $ARGUMENTS is empty, prompt the user for a question 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. 3d ago First seen · 14 lines · 14 tokens per session scan A a95572e942c5

Subscribe to this mod's changes

chat is a command published in the GitHub repository aws/agent-toolkit-for-aws (2,498 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 156 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.