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
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add aws/agent-toolkit-for-aws/plugin install aws-startup-advisorWrote 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/skills/aws/agent-toolkit-for-aws/llm-to-bedrock)<a href="https://agentmods.dev/skills/aws/agent-toolkit-for-aws/llm-to-bedrock"><img src="https://agentmods.dev/badge/skills/aws/agent-toolkit-for-aws/llm-to-bedrock/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/skills/aws/agent-toolkit-for-aws/llm-to-bedrock"><img src="https://agentmods.dev/badge/skills/aws/agent-toolkit-for-aws/llm-to-bedrock.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.00191 | $0.21796 |
| Opus 5.5 | $0.00076 | $0.08718 |
| Sonnet 5.5 | $0.00038 | $0.04359 |
| Haiku 4.5 | $0.00019 | $0.02180 |
Grade D, and why
llm-to-bedrock scanned grade D with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
printf '%s=%s\n' "$KEY_ENV_VAR" "$(printenv "$KEY_ENV_VAR")" > "$REPO/.saws-migrate/.source-provider-env" && chmod 600 "$REPO/.saws-migrate/.source-provider-env" Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
> `git tag -d saws-migrate-baseline`, and `rm -rf .saws-migrate .migration` removes all How it starts
The opening of the file, as written. The whole thing — 1,288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate to Bedrock (Assess + Execute)
Single-command AI migration: OpenAI / Gemini / Anthropic → Amazon Bedrock.
Requires the gcp-to-aws OR the azure-to-aws skill installed alongside this one. This
skill has no standalone Assess implementation — Phase A below runs Assess by directly reading
and executing whichever of those two skills is present's own phase instruction files in this
same session (the same inline-execution pattern agent-advisor uses for its migration-plan
phase: no cross-skill tool call, no turn boundary, and no dependency on your agent supporting a
Skill/subagent dispatch mechanism — reading a file works on any agent). There is no fallback
path that performs Assess itself if neither sibling is present. If you installed this skill on
its own (e.g. a single-skill npx skills add), install gcp-to-aws or azure-to-aws too
before using it.
The skill base directory is given in the "Base directory for this skill: X" line the harness
emits at load time. Call it <SKILL_BASE>. Derived paths:
$SCRIPTS=<SKILL_BASE>/scripts$HELPERS=<SKILL_BASE>/references/helpers(the former helper skills, now references)$ASSESS_SKILL/$ASSESS_BASE— resolved once, in Step 0b:$ASSESS_SKILLis whichever ofgcp-to-aws/azure-to-awsis installed alongside this skill (gcp-to-awspreferred when both are present), and$ASSESS_BASE=<SKILL_BASE>/../$ASSESS_SKILL— that sibling skill's own directory. Phase A reads its instruction files directly off this path; every relative reference inside an$ASSESS_SKILLfile (references/shared/...,references/phases/..., etc.) resolves under$ASSESS_BASE, exactly as it would if$ASSESS_SKILLwere running standalone.
Optional usage telemetry
Before starting or resuming, load references/vendored/telemetry/PROTOCOL.md and
run its read-only status check. Use the returned reporting mode rather than the
model's identity. Complete the existing notice exchange only when that protocol
requires it; unavailable or declined telemetry never blocks this skill.
What ships with it
47 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/helpers/bedrock-known-fixes/bedrock-known-fixes.md 2.1 KB
- references/helpers/bedrock-known-fixes/references/bedrock-iam-inference-profile.md 2.9 KB
- references/helpers/bedrock-known-fixes/references/bedrock-inference-profile-model-id.md 1.9 KB
- references/helpers/bedrock-known-fixes/references/bedrock-response-key-casing.md 990 B
- references/helpers/bedrock-known-fixes/references/bedrock-vision.md 1.3 KB
- references/helpers/bedrock-known-fixes/references/bedrock-vision.py.template 3.2 KB
- references/helpers/behavior-delta-detection/behavior-delta-detection.md 11 KB
- references/helpers/behavior-delta-detection/references/gemini-to-bedrock.md 6.1 KB
- references/helpers/behavior-delta-detection/references/openai-to-bedrock.md 14 KB
- references/helpers/dependency-conflict-resolution/dependency-conflict-resolution.md 6.0 KB
- references/helpers/resolve-bedrock-model-id/resolve-bedrock-model-id.md 10 KB
- references/helpers/run-source-model-baseline/run-source-model-baseline.md 19 KB
- references/vendored/telemetry/cli.py 1.4 KB runs code
- references/vendored/telemetry/consent/accept.py 2.0 KB runs code
- references/vendored/telemetry/consent/cli.py 2.7 KB runs code
- references/vendored/telemetry/consent/notice.py 2.3 KB runs code
- references/vendored/telemetry/consent/opt_out.py 1.8 KB runs code
- references/vendored/telemetry/consent/record.py 6.6 KB runs code
- references/vendored/telemetry/metric_emission/client.py 11 KB runs code
- references/vendored/telemetry/metric_emission/migration_attributes.py 22 KB runs code
- references/vendored/telemetry/metric_emission/migration.py 25 KB runs code
- references/vendored/telemetry/PROTOCOL.md 5.2 KB
- references/vendored/telemetry/version.json 25 B
- scripts/bedrock_pricing.py 16 KB runs code
- scripts/iam_policy.py 6.8 KB runs code
- scripts/image_input.py 3.8 KB runs code
- scripts/preflight_bedrock.py 15 KB runs code
- scripts/pyproject.toml 565 B
- scripts/render_report.py 5.6 KB runs code
- scripts/resolve_source_model.py 8.1 KB runs code
- scripts/schemas/analysis.json 3.6 KB
- scripts/schemas/delta-decisions.json 875 B
- scripts/schemas/eval.json 2.3 KB
- scripts/schemas/ingestion.json 1.6 KB
- scripts/schemas/rewrite.json 2.1 KB
- scripts/source_baseline.py 10 KB runs code
- scripts/test_bedrock_pricing.py 17 KB runs code
- scripts/test_delta_reference_schema.py 8.9 KB runs code
- scripts/test_iam_policy.py 9.5 KB runs code
- scripts/test_image_input.py 5.8 KB runs code
- scripts/test_preflight_bedrock.py 12 KB runs code
- scripts/test_render_report.py 6.3 KB runs code
- scripts/test_resolve_source_model.py 6.5 KB runs code
- scripts/test_source_baseline.py 8.2 KB runs code
- scripts/test_validate_result.py 13 KB runs code
- scripts/uv.lock 181 KB
- scripts/validate_result.py 7.3 KB runs code
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.
- 2d ago Changed · +71 lines 2365b91e94c8
- 6d ago Changed · +274 lines · -26 tokens per session 19e265fb8de8
- 8d ago Changed · +13 lines 0e4dc3b3d936
- 10d ago Changed · +36 lines d43afcba6698
- 13d ago Changed · -12 lines 2c7c5cce4337
- 15d ago Changed · +180 lines · +67 tokens per session 3749e69b5e47
- 16d ago Changed d6c504d0491f
- 17d ago Changed 5a2c66973b32
- 20d ago First seen · 726 lines · 150 tokens per session scan D fa6d020805c6
llm-to-bedrock is a skill published in the GitHub repository aws/agent-toolkit-for-aws (2,886 stars, last pushed yesterday), licensed Apache-2.0. It adds 191 tokens to every session and 21,796 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-26.
Other skills, from other repositories
llm-router-ops
Operate a self-hosted OpenAI-compatible LLM router — client-wiring per client, context-window ad gotcha, env-vs-persisted-config gotcha, why an unauth health probe should 401. Use wiring a client, adding a backend, diagnosing misbehavior.
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
prompt-engineer
Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
mcore-run-on-slurm
How to launch distributed Megatron-LM training jobs on a SLURM cluster. Covers a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDADEVICEMAXCONNECTIONS rules across hardware and parallelism modes, container conventions, monitoring, and per-rank failure diagnosis.