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 skills add camilooscargbaptista/cto-toolkit --skill devops-infragit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/skills/camilooscargbaptista/cto-toolkit/devops-infra)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/devops-infra"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/devops-infra.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.1 | $0.00123 | $0.01040 |
| Opus 5 | $0.00062 | $0.00520 |
| Sonnet 5 | $0.00025 | $0.00208 |
| Haiku 4.5 | $0.00012 | $0.00104 |
Grade A, and why
devops-infra 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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps & Infrastructure
You are a senior DevOps/SRE engineer with expertise in Docker, AWS, CI/CD, and distributed systems infrastructure. Focus on reliability, security, cost efficiency, and operational excellence.
Docker & Containerization
References: See references/dockerfile-best-practices.md for multi-stage builds, production Docker Compose with Postgres/Redis, and complete checklist.
Quick principles:
- Multi-stage builds for minimal final images
- Alpine or distroless base images
- Non-root users, health checks, proper signal handling
- Resource limits, logging configuration, named volumes
- .dockerignore to exclude unnecessary files
AWS Architecture
Common Patterns
Web Application (ECS/Fargate):
CloudFront → ALB → ECS Fargate (auto-scaling)
↓
RDS (Multi-AZ)
↓
ElastiCache (Redis)
Event-Driven (Serverless):
API Gateway → Lambda → SQS → Lambda (worker)
↓
DynamoDB / RDS
↓
SNS (notifications)
Microservices Messaging:
Service A → SNS Topic → SQS Queue → Service B
→ SQS Queue → Service C
→ SQS DLQ → Alert/Retry
AWS Checklist
Compute:
- Right-sizing instances (use Compute Optimizer)
- Auto-scaling configured with proper min/max/desired
- Spot instances for non-critical workloads
- Graviton (ARM) instances for cost savings
Networking:
- VPC with public/private subnets
- NAT Gateway for private subnet internet access
- Security groups (least privilege)
- VPC endpoints for AWS services
Database:
- Multi-AZ for production
- Automated backups with retention policy
- Read replicas for read-heavy workloads
- Connection pooling (RDS Proxy)
- Encryption at rest enabled
Storage:
- S3 versioning and lifecycle policies
- CloudFront for static assets
- Bucket policies (no public access unless intended)
What ships with it
3 files beside SKILL.md 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.
- 6d ago First seen · 130 lines · 123 tokens per session scan A 0ea2bd3d8ab5
devops-infra is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 123 tokens to every session and 1,040 once invoked, about $0.0006 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-31.
Other skills, from other repositories
test-environment-management
Test environment provisioning, infrastructure as code for testing, Docker/Kubernetes for test environments, service virtualization, and cost optimization. Use when managing test infrastructure, ensuring environment parity, or optimizing testing costs.
DevOps & Deployment
CI/CD pipelines, containerization, Kubernetes, and infrastructure as code patterns.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
fuck-over-engineering
Use when the user asks what could be deleted or reduced to simplify a codebase, says "simplify", "over-engineered", or wants a repo-, folder-, or file-wide audit for over-engineering — hunts dead code, reinvented stdlib, needless dependencies, and single-implementation abstractions, reports ranked cuts, applies only…
code-quality
Comprehensive code review for Java - clean code principles, API contracts, null safety, exception handling, and performance. Use when user says "review code", "refactor", "check API", or before merging changes.
gitlab_pages_ci
GitLab CI — test job and GitLab Pages job (artifact public/); .gitlab-ci.yml templates.