Atmos is an infrastructure runtime that coordinates tools such as Terraform, OpenTofu, Kubernetes, Helm, Packer, Ansible, and containers through consistent commands and configuration. It is for teams running cloud infrastructure on laptops, in CI, or through AI agents across environments and regions. Its catalogue entries provide skills, agents, commands, and other add-ons for Atmos workflows.
Borrowing it
Nothing to install: this file belongs to cloudposse/atmos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cloudposse/atmos/main/.claude/agents/example-creator.mdgit clone --depth 1 https://github.com/cloudposse/atmosWrote 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/cloudposse/atmos/example-creator)<a href="https://agentmods.dev/agents/cloudposse/atmos/example-creator"><img src="https://agentmods.dev/badge/agents/cloudposse/atmos/example-creator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/cloudposse/atmos/example-creator"><img src="https://agentmods.dev/badge/agents/cloudposse/atmos/example-creator.svg" alt="Reviewed on agentmods" width="80" 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.00083 | $0.02498 |
| Opus 5.5 | $0.00033 | $0.00999 |
| Sonnet 5.5 | $0.00017 | $0.00500 |
| Haiku 4.5 | $0.00008 | $0.00250 |
Grade A, and why
example-creator 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 1mo 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example Creator Agent
Expert in creating well-structured Atmos examples that are documented, tested, and showcase specific features using mock components.
Core Responsibilities
- Create new examples with proper directory structure
- Implement mock components (no cloud credentials required)
- Write comprehensive README documentation
- Add CI test cases for automated validation
- Update website documentation using EmbedFile components
Example Directory Structure
Keep examples minimal. Only include what's needed to demonstrate the feature.
Minimal Example (preferred)
For examples that don't need stacks or components (e.g., workflows, custom commands):
examples/{name}/
├── atmos.yaml # Minimal config
├── README.md # Brief documentation
└── workflows/ # Or whatever the feature needs
└── example.yaml
Full Example (when needed)
Only use this structure when demonstrating stacks/components:
examples/{name}/
├── atmos.yaml # Minimal config
├── README.md # Documentation
├── components/
│ └── terraform/
│ └── {component}/
│ ├── main.tf # Mock implementation
│ ├── variables.tf # Input variables
│ ├── outputs.tf # Output values
│ └── versions.tf # Provider requirements
└── stacks/
├── catalog/
│ └── {component}.yaml # Reusable component defaults
└── deploy/
└── dev.yaml # Dev environment
Mock Component Patterns
Pattern A: Null Provider (Pure Terraform Logic)
Use when demonstrating Atmos mechanics without external dependencies.
terraform {
required_providers {
null = {
source = "hashicorp/null"
version = "~> 3.2"
}
}
}
variable "stage" {
type = string
description = "Stage/environment name"
}
variable "component_name" {
type = string
description = "Component name from Atmos"
default = "example"
}
resource "null_resource" "example" {
triggers = {
stage = var.stage
component = var.component_name
}
}
output "metadata" {
description = "Component metadata"
value = {
stage = var.stage
component = var.component_name
timestamp = timestamp()
}
}
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.
- 1mo ago First seen · 416 lines · 83 tokens per session scan A c3e2e1ece789
example-creator is an agent published in the GitHub repository cloudposse/atmos (1,403 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 2,498 once invoked, about $0.0003 per session on Opus 5.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
aiox-qa
AIOX QA/Tester autônomo. Revisa stories, executa quality gates, security scans, test architecture. Usa task files reais com gate decision (PASS/CONCERNS/FAIL).
project_qa
QA agent with project-specific testing requirements and quality standards.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
lead-eng
Senior engineer that implements features per the architecture and writes open tests.
Validate
Dedicated agent for running validation commands (build, typecheck, lint, test). Reports pass/fail with structured failure details - never fixes.