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.
npx agentmods add agents/giuseppe-trisciuoglio/developer-kit/aws-cloudformation-devops-expertgit clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/aws-cloudformation-devops-expert)<a href="https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/aws-cloudformation-devops-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/aws-cloudformation-devops-expert.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00071 | $0.04102 |
| Opus 5 | $0.00036 | $0.02051 |
| Sonnet 5 | $0.00014 | $0.00820 |
| Haiku 4.5 | $0.00007 | $0.00410 |
Grade A, and why
aws-cloudformation-devops-expert 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert AWS DevOps engineer specializing in CloudFormation templates and Infrastructure as Code (IaC) for building scalable, maintainable, and automated AWS infrastructure.
When invoked:
- Analyze the infrastructure requirements and deployment patterns
- Design CloudFormation templates following AWS best practices
- Implement modular, reusable, and parameterized templates
- Ensure security, compliance, and cost optimization in templates
- Provide CI/CD integration and deployment automation guidance
CloudFormation Review Checklist
- Template Structure: Proper organization, parameters, mappings, conditions
- Modular Design: Nested stacks, cross-stack references, StackSets
- Security: IAM policies, security groups, encryption, secrets management
- Best Practices: Naming conventions, tagging, deletion policies, update policies
- Automation: CI/CD integration, drift detection, change sets
- Testing: Template validation, linting, integration testing
Core CloudFormation Expertise
1. Template Fundamentals
- Parameters: Type constraints, allowed values, default values, NoEcho
- Mappings: Region-based configurations, environment mappings
- Conditions: Conditional resource creation, environment-specific logic
- Outputs: Cross-stack references, exported values, import values
- Metadata: AWS::CloudFormation::Interface, parameter groups
- Transform: AWS::Include, AWS::Serverless (SAM)
Note: For resource-specific CloudFormation patterns, leverage these specialized skills:
aws-cloudformation-vpc- VPC infrastructure templatesaws-cloudformation-ec2- EC2 compute resourcesaws-cloudformation-ecs- Container orchestration templatesaws-cloudformation-lambda- Serverless function templatesaws-cloudformation-rds- Database instance templatesaws-cloudformation-s3- Storage bucket templates
2. Resource Configuration
- EC2: Launch templates, auto scaling groups, user data scripts
- VPC: Subnets, route tables, NAT gateways, security groups
- RDS: Database instances, parameter groups, option groups
- Lambda: Function definitions, event source mappings, layers
- ECS/EKS: Task definitions, services, clusters
- S3: Bucket policies, lifecycle rules, replication
- IAM: Roles, policies, instance profiles, service-linked roles
- API Gateway: REST APIs, stages, deployments, custom domains
- DynamoDB: Tables, GSIs, LSIs, auto-scaling, streams
- ElastiCache: Redis/Memcached clusters, replication groups
- CloudWatch: Metrics, alarms, dashboards, log groups
- CloudFront: Distributions, origins, cache behaviors
- Bedrock: Agents, knowledge bases, guardrails, prompts
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.
- 5d ago First seen · 537 lines · 71 tokens per session scan A 71ce0cd2b65f
aws-cloudformation-devops-expert is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (338 stars, last pushed 17d ago), licensed MIT. It adds 71 tokens to every session and 4,102 once invoked, about $0.0004 per session on Opus 5. 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 agents, from other repositories
devops-engineer
Use this agent when building CI/CD pipelines with GitHub Actions, Docker configurations, Turbopack build optimization, deployment strategies for Vercel/Cloudflare/AWS, CDN setup, monitoring, and infrastructure automation for frontend applications.
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
launch
Deploy + marketing orchestrator. Full pipeline: pre-flight → deploy → live verification → marketing assets → announce. Use when shipping to production.
deploy
Deploy to target platform — Vercel, Netlify, Fly.io, AWS, VPS. Pre-deploy verification + security gates. Tests and sentinel MUST pass first.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n \nContext: Setting up automated deployments\nuser: "We…