setup-devops-agent

A setup command for connecting an AWS DevOps Agent to your project. It configures either a bearer token or AWS Signature Version 4 credentials.

In plain words
What is it for?
Use it when preparing a project to work with the AWS DevOps Agent and its authentication credentials.
Why use it?
It removes the need to work out and enter the DevOps Agent connection settings manually.

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/setup-devops-agent
Clone the repo
git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 39 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.00009 $0.00039
Opus 5 $0.00005 $0.00019
Sonnet 5 $0.00002 $0.00008
Haiku 4.5 $0.00001 $0.00004

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

Security

Grade A, and why

setup-devops-agent 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 2d 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/setup-devops-agent.md · 6 lines

What it actually says

Invoke the setup-devops-agent skill to configure Bearer token or SigV4 credentials for the DevOps Agent.

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. 2d ago First seen · 6 lines · 9 tokens per session scan A 0822ed43800a

Subscribe to this mod's changes

setup-devops-agent is a command published in the GitHub repository aws/agent-toolkit-for-aws (2,477 stars, last pushed 4d ago), licensed Apache-2.0. It adds 9 tokens to every session and 39 once invoked, about $0.0000 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.