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 giuseppe-trisciuoglio/developer-kitnpx agentmods add plugins/giuseppe-trisciuoglio/developer-kit/developer-kit-awsgit clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitGrade A, and why
developer-kit-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": "developer-kit-aws",
"version": "4.0.0",
"description": "AWS infrastructure and CloudFormation expertise",
"author": {
"name": "Giuseppe Trisciuoglio",
"email": "[email protected]"
},
"homepage": "https://github.com/giuseppe-trisciuoglio/developer-kit",
"repository": "https://github.com/giuseppe-trisciuoglio/developer-kit.git",
"license": "MIT",
"keywords": [
"aws",
"cloudformation",
"infrastructure",
"iac"
],
"agents": [
"./agents/aws-solution-architect-expert.md",
"./agents/aws-cloudformation-devops-expert.md",
"./agents/aws-architecture-review-expert.md"
],
"commands": [],
"skills": [
"./skills/aws-cloudformation/aws-cloudformation-vpc",
"./skills/aws-cloudformation/aws-cloudformation-ec2",
"./skills/aws-cloudformation/aws-cloudformation-lambda",
"./skills/aws-cloudformation/aws-cloudformation-iam",
"./skills/aws-cloudformation/aws-cloudformation-s3",
"./skills/aws-cloudformation/aws-cloudformation-rds",
"./skills/aws-cloudformation/aws-cloudformation-dynamodb",
"./skills/aws-cloudformation/aws-cloudformation-ecs",
"./skills/aws-cloudformation/aws-cloudformation-auto-scaling",
"./skills/aws-cloudformation/aws-cloudformation-cloudwatch",
"./skills/aws-cloudformation/aws-cloudformation-cloudfront",
"./skills/aws-cloudformation/aws-cloudformation-security",
"./skills/aws-cloudformation/aws-cloudformation-elasticache",
"./skills/aws-cloudformation/aws-cloudformation-bedrock",
"./skills/aws-cloudformation/aws-cloudformation-task-ecs-deploy-gh",
"./skills/aws/aws-drawio-architecture-diagrams",
"./skills/aws/aws-cli-beast",
"./skills/aws/aws-sam-bootstrap",
"./skills/aws/aws-cost-optimization"
]
}
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 · 46 lines scan A 63315f6aca11
developer-kit-aws is a plugin published in the GitHub repository giuseppe-trisciuoglio/developer-kit (337 stars, last pushed 14d 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
contentful
Agent skills for Contentful apps, APIs, migrations, and personalization.
opentikz
TikZ resources for academic conceptual diagrams.
market-intelligence
Competitive landscape, incentive mapping, positioning, and information asymmetry — strategic-group mapping with mobility-barrier analysis, incentive-driven behavior prediction, positioning trade-off discipline, information-asymmetry analysis, and game-theory-grounded competitive response forecasting.
consulting
Strategic narrative, hypothesis-driven problem solving, and deliverable craft — Minto pyramid structure, hypothesis trees, hypothesis-driven workplans, deck outlines, exec memos, so-what sharpening, and doc/deck review.
capacitor-core
Core Capacitor skills for best practices, plugin selection, and MCP automation.
ls-code
Language-agnostic coding skills.