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 ferdinandobons/AWSBestPracticesSkillnpx agentmods add plugins/ferdinandobons/awsbestpracticesskill/awsbestpracticesskillgit clone --depth 1 https://github.com/ferdinandobons/AWSBestPracticesSkillGrade A, and why
aws-best-practices 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": "aws-best-practices",
"displayName": "AWS Best Practices",
"version": "0.1.5",
"description": "Unofficial source-linked AWS best practices for every service, organized by Well-Architected pillar, use case, and scenario-targeted answer flow. Independent project, not affiliated with AWS.",
"author": {
"name": "Ferdinando Bons"
},
"homepage": "https://github.com/ferdinandobons/AWSBestPracticesSkill",
"repository": "https://github.com/ferdinandobons/AWSBestPracticesSkill",
"license": "MIT",
"keywords": [
"aws",
"best-practices",
"well-architected",
"security",
"cost-optimization",
"reliability",
"skill"
]
}
What ships with it
1 file beside plugin.json 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.
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 · 22 lines scan A 1ee71a9db319
aws-best-practices is a plugin published in the GitHub repository ferdinandobons/AWSBestPracticesSkill (37 stars, last pushed 1mo ago), licensed MIT. 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
aws-transform
Migrate, modernize, and upgrade codebases to AWS. Transforms .NET Framework to .NET 8/10, mainframe COBOL to Java, VMware VMs to EC2, SQL Server to Aurora, and upgrades Java/Python/Node.js versions and AWS SDKs. AWS Transform - continuous modernization analyzes codebases for tech debt, security issues, and upgrade…
amazon-location-service
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.
aws-amplify
Build full-stack apps with AWS Amplify Gen 2 using guided workflows for authentication, data models, storage, GraphQL APIs, and Lambda functions.
aws-serverless
Design, build, deploy, test, and debug serverless applications with AWS Serverless services.
defang
Deploy Docker Compose apps to your own cloud account using Defang. Includes a /defang:deploy skill and Defang MCP server integration.
cdkd-skills
Deploy AWS CDK apps safely with cdkd (CDK Direct). Guides AI coding agents through installing cdkd and bootstrapping, previewing, deploying, verifying, and destroying dev/test stacks with explicit safety boundaries.