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/startupsnpx agentmods add plugins/awslabs/startups/migration-to-awsgit clone --depth 1 https://github.com/awslabs/startupsGrade A, and why
migration-to-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 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.
What it actually says
{
"name": "migration-to-aws",
"version": "1.5.0",
"description": "This no-cost tool assesses your current cloud provider's usage, geography, and billing data to estimate and compare AWS services and pricing, and recommends migration or continued use of your current provider. Supports GCP and Heroku migrations. AWS pricing is based on current published pricing and may vary over time. The tool may generate a .migration folder containing comparison and migration execution data, which you may delete upon completion or use to migrate to AWS.",
"author": {
"name": "Amazon Web Services"
},
"license": "Apache-2.0",
"keywords": [
"aws",
"gcp",
"google-cloud",
"cloud-run",
"cloud-sql",
"vertex-ai",
"gemini",
"migration",
"cloud-migration",
"move-to-aws",
"switch-to-aws",
"terraform",
"fargate",
"rds",
"aurora",
"eks",
"bedrock",
"ai-migration",
"openai",
"openai-to-bedrock",
"langchain",
"langgraph",
"crewai",
"autogen",
"agentic",
"agents",
"llm-migration",
"cost-estimation",
"cost-comparison",
"pricing-comparison",
"agent-runtime",
"agentcore",
"lambda-microvms",
"deploy-ai-agent",
"agent-architecture",
"choose-agent-runtime",
"agentcore-vs-lambda",
"where-to-run-my-agent",
"add-agentcore-services",
"bedrock-migration",
"openai-to-bedrock-execute",
"llm-to-bedrock",
"rewrite-sdk-calls",
"bedrock-code-rewrite",
"ai-migration-execute",
"temporal",
"temporal-cloud",
"temporal-workers",
"temporal-to-aws",
"durable-execution"
]
}
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 First seen · 62 lines scan A 8ed173cc1599
migration-to-aws is a plugin published in the GitHub repository awslabs/startups (16 stars, last pushed today), 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
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.