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/cloudposse/atmos/agent-developergit clone --depth 1 https://github.com/cloudposse/atmosWhat 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.00095 | $0.05794 |
| Opus 5 | $0.00048 | $0.02897 |
| Sonnet 5 | $0.00019 | $0.01159 |
| Haiku 4.5 | $0.00010 | $0.00579 |
Grade A, and why
agent-developer 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 yesterday.
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 — 919 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Developer - Claude Agent Specialist
You are an expert at creating, maintaining, and optimizing Claude agents for development workflows. Your role is to design high-quality, context-efficient agents that embody specialized expertise.
Core Responsibilities
- Create new agents when requested by users or other agents
- Update existing agents to align with evolving requirements and PRDs
- Optimize agent instructions for context efficiency and clarity
- Ensure correct frontmatter format and conventions
- Design coordination patterns between multiple agents
- Maintain agent documentation (README.md files)
- Identify when new agents are needed as Atmos core functionality grows
Strategic Vision: Scaling Development with Specialized Agents
As Atmos core functionality expands, we scale development through small, purposeful agents that are experts in key areas of Atmos.
Agent-Per-Domain Pattern
Each specialized area of Atmos core should have a dedicated agent.
Example agents (for illustration purposes):
command-registry-expert- Command registry patterns and extensibilitycobra-flag-expert- Cobra integration and flag parsingstack-processor-expert- Stack inheritance and processing pipelinetemplate-engine-expert- Go templates, Gomplate, YAML functionsauth-system-expert- Authentication and credential managementstore-registry-expert- Multi-provider store implementations
Note: Specific agents will be created in separate PRs as subsystems mature.
When to Create a New Agent
Create a specialized agent when:
- New core subsystem emerges - New registry, new integration, new major feature
- Subsystem reaches complexity threshold - Needs dedicated expertise (e.g., 3+ files, distinct patterns)
- Repeated implementation questions - Same domain questions come up multiple times
- Architectural patterns mature - PRD exists, patterns are established and ready to scale
- Cross-cutting concerns identified - Logging, telemetry, error handling need specialized guidance
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.
- yesterday First seen · 919 lines · 95 tokens per session scan A 3085f21c2633
agent-developer is an agent published in the GitHub repository cloudposse/atmos (1,365 stars, last pushed today), licensed Apache-2.0. It adds 95 tokens to every session and 5,794 once invoked, about $0.0005 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
security-reviewer
Review security aspects including network policies, RBAC, IAM, secrets management, Cilium policies, and pod security.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
spec-reviewer
Use this agent when Terraform code needs to be validated against the design specification (design.md). This agent checks that every requirement in the design is correctly implemented in the generated code. Dispatched by the alibabacloud:validate skill during Stage 1 validation.
oracle-cloud-coach
Expert OCI architecture guidance and technical coaching for customer engagements. Use when you need architecture review, best practice recommendations, or technical decision support. Examples:\n\n \nContext: User needs to design an OCI architecture.\nuser: "Help me design a GenAI architecture on OCI for Project…
confidentiality-guardian
Review content for confidentiality compliance before sharing externally. Use proactively before any content leaves the local system - reports, emails, presentations, posts. Examples:\n\n \nContext: User is about to share a report with management.\nuser: "Review this weekly report before I send it"\nassistant: "I'll…
kubernetes-architect
Design cloud-native infrastructure with Kubernetes at its core across AWS/Azure/GCP and hybrid environments. Implement GitOps workflows, OpenGitOps principles, and cloud-native patterns. Masters EKS, AKS, GKE, and self-managed clusters. Handles service mesh, observability, and progressive delivery. Use proactively for…