A guided toolkit for building full-stack applications with AWS Amplify Gen 2, Amazon Web Services’ development framework. It covers user sign-in, data, file storage, GraphQL APIs, and Lambda functions, which are small pieces of code run by AWS.

Use it to create applications with accounts, stored data, uploaded files, GraphQL services, and AWS Lambda back-end logic.

It brings common application back-end tasks into one AWS-based workflow, so developers do not have to assemble authentication, databases, file storage, APIs, and server-side functions separately.

aws-amplify — Plugin by awslabs

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.

Claude Code

/plugin marketplace add awslabs/agent-plugins

agentmods

npx agentmods add plugins/awslabs/agent-plugins/aws-amplify

Clone the repo

git clone --depth 1 https://github.com/awslabs/agent-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

aws-amplify 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 yesterday.

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-amplify/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "author": {
    "name": "Amazon Web Services"
  },
  "description": "Build full-stack apps with AWS Amplify Gen 2 using guided workflows for authentication, data models, storage, GraphQL APIs, and Lambda functions.",
  "homepage": "https://github.com/awslabs/agent-plugins",
  "keywords": [
    "aws",
    "amplify",
    "fullstack",
    "authentication",
    "data",
    "storage",
    "graphql",
    "functions"
  ],
  "license": "Apache-2.0",
  "name": "aws-amplify",
  "repository": "https://github.com/awslabs/agent-plugins",
  "version": "1.0.0"
}

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.

yesterday First seen · 22 lines scan A bc8a59994567

Subscribe to this mod's changes

aws-amplify is a plugin published in the GitHub repository awslabs/agent-plugins (876 stars, last pushed 5d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Backend and APIs DevOps and cloud agent-plugins agent-skills agents aws coding-agent-skills coding-agents

aws-amplify

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

ctx

ctx

aai-plugins

setup

system

claude-forge