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 cosmicstack-labs/mercury-agent-skills --skill cloud-architecturegit clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skillsWrote 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/cosmicstack-labs/mercury-agent-skills/cloud-architecture)<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/cloud-architecture"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/cloud-architecture/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/cosmicstack-labs/mercury-agent-skills/cloud-architecture"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/cloud-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00553 |
| Opus 5 | $0.00010 | $0.00277 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
cloud-architecture 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 8d 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.
What it actually says
Cloud Architecture
Design resilient, cost-effective cloud architectures.
Design Pillars
| Pillar | Focus | Pattern |
|---|---|---|
| Reliability | Fault tolerance, recovery | Multi-AZ, redundancy, auto-healing |
| Security | Defense in depth | IAM, encryption, network segmentation |
| Cost | Efficiency, waste reduction | Right-sizing, reserved instances, autoscaling |
| Performance | Speed, scalability | CDN, caching, horizontal scaling |
| Operational | Manageability, automation | IaC, CI/CD, runbooks |
VPC Design
Multi-Tier Architecture
Internet → WAF → ALB → App Tier (private) → DB Tier (private)
↕
Auto Scaling
Best Practices
- Use multiple AZs (minimum 3)
- Private subnets for apps and databases
- Public subnets only for load balancers and bastions
- NACLs for subnet-level rules, Security Groups for instance-level
- VPC peering or Transit Gateway for multi-VPC
High Availability
- Compute: Multi-AZ Auto Scaling groups, spot + on-demand mix
- Database: Multi-AZ RDS, Aurora read replicas
- Storage: S3 (11 9's durability), EBS snapshots
- DNS: Route53 with health-check based failover
- CDN: CloudFront/CloudFlare for global distribution
Disaster Recovery
| Strategy | RTO | RPO | Cost |
|---|---|---|---|
| Backup & Restore | Hours | 24h | $ |
| Pilot Light | Minutes | 1h | $$ |
| Warm Standby | Seconds | Minutes | $$$ |
| Active-Active | Seconds | Seconds | $$$$ |
DR Plan
- Document runbooks for each scenario
- Test failover quarterly
- Automate recovery with IaC
- Store backups in separate region
- Encrypt everything
Cost Optimization
- Right-size instances (use Compute Optimizer)
- Reserved Instances / Savings Plans for steady state
- Spot instances for fault-tolerant workloads
- S3 lifecycle policies (transition to Glacier)
- Delete unused resources (EBS, EIP, ELB)
- Monitor with Cost Explorer + budgets + alerts
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.
- 8d ago First seen · 71 lines · 20 tokens per session scan A 10c681136dec
cloud-architecture is a skill published in the GitHub repository cosmicstack-labs/mercury-agent-skills (470 stars, last pushed 17d ago), licensed MIT. It adds 20 tokens to every session and 553 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-09-03.
Other skills, from other repositories
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
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…
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
google-cloud-filestore-auditing
Audits Google Cloud Filestore instances across projects for disaster recovery readiness (missing or stale backups), security access governance (overly permissive NFS export rules, 0.0.0.0/0 exposure, missing ROOTSQUASH), and reliability compliance (Physical Zone Isolation PZI and Physical Zone Separation PZS). Use…