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 aws/agent-toolkit-for-awsnpx agentmods add plugins/aws/agent-toolkit-for-aws/aws-agents-for-devsecopsgit clone --depth 1 https://github.com/aws/agent-toolkit-for-awsGrade A, and why
aws-agents-for-devsecops 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-agents-for-devsecops",
"description": "Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.",
"version": "1.0.0",
"author": {
"name": "Amazon Web Services"
},
"homepage": "https://docs.aws.amazon.com/devopsagent/latest/userguide/",
"repository": "https://github.com/aws/agent-toolkit-for-aws/tree/main/plugins/aws-agents-for-devsecops",
"license": "Apache-2.0",
"keywords": [
"Amazon Web Services",
"agentspace",
"api-testing",
"appsec",
"architecture-review",
"aws",
"cloudwatch",
"code-review",
"cost-optimization",
"devops",
"devsecops",
"incident",
"investigation",
"is-my-code-secure",
"mcp",
"observability",
"operations",
"penetration-test",
"pentest",
"pre-merge",
"qa",
"release",
"release-analysis",
"release-readiness",
"release-testing",
"reliability",
"remediation",
"risk-analysis",
"security",
"security-scan",
"security-vulnerabilities",
"testing",
"threat-model",
"topology",
"uat",
"ui-testing"
]
}
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 · 50 lines scan A dc8734186504
aws-agents-for-devsecops is a plugin published in the GitHub repository aws/agent-toolkit-for-aws (2,498 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.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins marketplace
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.
ui-ux-pro-max
UI/UX design intelligence. Searchable local database with 84 styles, 192 palettes, 74 font pairings, 25 charts, and 22 stacks (React, Next.js, Vue, Nuxt.js, Nuxt UI, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP…