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 MonumentalSystems/Atlas-Agent-Teams --skill cloud-platformsgit clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/cloud-platforms)<a href="https://agentmods.dev/skills/monumentalsystems/atlas-agent-teams/cloud-platforms"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/cloud-platforms/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/skills/monumentalsystems/atlas-agent-teams/cloud-platforms"><img src="https://agentmods.dev/badge/skills/monumentalsystems/atlas-agent-teams/cloud-platforms.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.00016 | $0.01771 |
| Opus 5 | $0.00008 | $0.00886 |
| Sonnet 5 | $0.00003 | $0.00354 |
| Haiku 4.5 | $0.00002 | $0.00177 |
Grade A, and why
cloud-platforms 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 9d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Platforms
AWS Services and Best Practices
Compute Services
-
EC2 (Elastic Compute Cloud): Virtual servers in the cloud
- Use instance types appropriate for workload requirements
- Implement Auto Scaling Groups for elasticity
- Use Spot Instances for fault-tolerant, interruptible workloads
- Leverage EC2 Fleet for diverse instance strategies
-
Lambda: Serverless compute service
- Ideal for event-driven architectures
- Use for short-lived, stateless functions
- Implement dead-letter queues for failed invocations
- Monitor with CloudWatch metrics and logs
-
ECS (Elastic Container Service): Container orchestration
- Use Fargate for serverless container execution
- Implement task definitions with resource limits
- Use service auto-scaling based on metrics
- Configure load balancing with ALB/NLB
-
EKS (Elastic Kubernetes Service): Managed Kubernetes
- Use managed node groups for simplified operations
- Implement pod autoscaling (HPA, VPA)
- Use AWS VPC CNI for networking
- Integrate with IAM for service accounts
Storage Services
-
S3 (Simple Storage Service): Object storage
- Use lifecycle policies for cost optimization
- Implement versioning for data protection
- Use S3 Transfer Acceleration for faster uploads
- Configure CORS for cross-origin access
- Enable S3 Event Notifications for automation
-
EBS (Elastic Block Store): Block storage
- Choose volume type based on workload (gp3, io2, etc.)
- Use multi-attach for high availability
- Implement snapshots for backup
- Monitor volume metrics for performance
Database Services
-
RDS (Relational Database Service): Managed relational databases
- Use Multi-AZ deployments for high availability
- Enable read replicas for scaling reads
- Use automated backups and point-in-time recovery
- Implement parameter groups for configuration
-
DynamoDB: NoSQL database
- Design partition keys for even distribution
- Use on-demand mode for unpredictable workloads
- Implement TTL for automatic data expiration
- Use DynamoDB Accelerator (DAX) for caching
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.
- 9d ago First seen · 217 lines · 16 tokens per session scan A 84f09051f59a
cloud-platforms is a skill published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 28d ago), licensed MIT. It adds 16 tokens to every session and 1,771 once invoked, about $0.0001 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 skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…