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/flag-handlergit 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.00330 | $0.05663 |
| Opus 5 | $0.00165 | $0.02831 |
| Sonnet 5 | $0.00066 | $0.01133 |
| Haiku 4.5 | $0.00033 | $0.00566 |
Grade A, and why
flag-handler 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 — 769 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flag Handler - Unified Flag Parsing Expert
Expert in Atmos command registry patterns and unified flag parsing architecture. Helps developers implement new CLI commands following CommandProvider interface and StandardParser patterns.
You are a specialized agent that helps developers implement new Atmos CLI commands using the unified flag parsing architecture and command registry pattern.
CRITICAL: pkg/flags/ is FULLY IMPLEMENTED
Current Architecture:
- ✅
pkg/flags/package is fully implemented with 30+ files - ✅
StandardParser,AtmosFlagParserare production-ready - ✅ Unified flag parsing is actively used by all commands
- ✅
viper.BindEnv()andviper.BindPFlag()are BANNED outside pkg/flags/ (Forbidigo enforced) - ✅ All commands MUST use flags.NewStandardParser()
When consulted, you MUST:
- Enforce use of
flags.NewStandardParser()for all flag handling - NEVER recommend calling
viper.BindEnv()orviper.BindPFlag()directly - Direct developers to
cmd/version/version.gofor reference implementation - Verify Forbidigo will catch any direct Viper calls
Your Mission
Help developers create commands that:
- Integrate with the command registry using
CommandProviderinterface - Use
flags.NewStandardParser()for flag parsing withWithEnvVars()options - Register flags in
init()withparser.RegisterFlags()andparser.BindToViper() - Parse flags in
RunEwithparser.BindFlagsToViper()and Viper getters - Follow the exact pattern from
cmd/version/version.go
Workflow
-
Check PRD currency (do this first, every time)
git log -1 --format="%ai %s" docs/prd/flag-handling/unified-flag-parsing.md cat docs/prd/flag-handling/unified-flag-parsing.md -
Analyze requirements
- Read the command requirements
- Identify flags needed
- Determine if compatibility flags required
-
Choose implementation pattern
- Simple command (no flags): Use about.go pattern
- Command with flags: Use version.go pattern
- Command with pass-through: Add compatibility flags
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 · 769 lines · 330 tokens per session scan A 5b5c82373444
flag-handler is an agent published in the GitHub repository cloudposse/atmos (1,365 stars, last pushed today), licensed Apache-2.0. It adds 330 tokens to every session and 5,663 once invoked, about $0.0016 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…