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.
/plugin marketplace add awslabs/agent-pluginsnpx agentmods add plugins/awslabs/agent-plugins/marketplacegit clone --depth 1 https://github.com/awslabs/agent-pluginsGrade A, and why
agent-plugins-for-aws 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.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"metadata": {
"description": "Agent Plugins for AWS equip AI coding agents with the skills to help you architect, deploy, and operate on AWS.",
"version": "1.1.0"
},
"name": "agent-plugins-for-aws",
"owner": {
"email": "[email protected]",
"name": "Amazon Web Services"
},
"plugins": [
{
"category": "location",
"description": "Guide developers through adding maps, places search, geocoding, routing, and other geospatial features with Amazon Location Service, including authentication setup, SDK integration, and best practices.",
"keywords": [
"location",
"maps",
"geocoding",
"routing",
"places",
"geofencing",
"tracking",
"amazon-location",
"maplibre",
"address",
"coordinates"
],
"name": "amazon-location-service",
"source": "./plugins/amazon-location-service",
"tags": [
"aws",
"location",
"maps",
"geospatial"
],
"version": "1.0.0"
},
{
"category": "fullstack",
"description": "Build full-stack apps with AWS Amplify Gen 2 using guided workflows for authentication, data models, storage, GraphQL APIs, and Lambda functions.",
"keywords": [
"aws",
"amplify",
"fullstack",
"authentication",
"data",
"storage",
"graphql",
"functions"
],
"name": "aws-amplify",
"source": "./plugins/aws-amplify",
"tags": [
"aws",
"amplify",
"fullstack"
],
"version": "1.0.0"
},
{
"category": "development",
"description": "Design, build, deploy, test, and debug serverless applications with AWS Serverless services.",
"keywords": [
"aws",
"aws agent skills",
"amazon",
"serverless",
"lambda",
"durable functions",
"managed-instances",
"lmi",
"capaWhat 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 · 249 lines scan A fa06bbceeaf8
agent-plugins-for-aws 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.
Other plugins, from other repositories
ctx
Plugin marketplace listing 1 plugin: ctx.
ctx
Fast local search and 'git blame' for agent sessions.
aai-plugins
Production-ready workflow framework for Claude Code - structured development patterns, work management, and quality automation.
setup
Project initialization and Claude Code configuration.
system
System health, maintenance, and project setup.
claude-forge
Plugin marketplace listing 5 plugins: ctk, dtk, atk, ftk, etk.