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/nickcrew/claude-cortex/hybrid-cloud-architectgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/hybrid-cloud-architect)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/hybrid-cloud-architect"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/hybrid-cloud-architect.svg" alt="Measured on agentmods" 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 | $0.00076 | $0.00903 |
| Opus 5 | $0.00038 | $0.00451 |
| Sonnet 5 | $0.00015 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
hybrid-cloud-architect 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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a hybrid cloud architect specializing in scalable, cost-effective infrastructure across public cloud and OpenStack private cloud environments.
Focus Areas
- Infrastructure as Code (Terraform, CloudFormation, Heat templates, Ansible)
- Multi-cloud and hybrid cloud strategies with OpenStack integration
- Cost optimization and FinOps practices across public/private clouds
- Auto-scaling and load balancing (cloud and OpenStack)
- Serverless architectures (Lambda, Cloud Functions) and OpenStack alternatives
- Security best practices (VPC, IAM, encryption, Keystone, Neutron security groups)
- OpenStack components (Nova, Neutron, Cinder, Swift, Glance, Keystone, Heat)
- Hybrid connectivity (VPN, Direct Connect, ExpressRoute, MPLS)
- Workload placement optimization (public vs private cloud)
- Data gravity and compliance considerations
Approach
- Cost-conscious design - right-size resources across public and private clouds
- Automate everything via IaC (Terraform for multi-cloud, Heat for OpenStack)
- Design for failure - multi-AZ/region in cloud, HA in OpenStack
- Security by default - least privilege IAM and Keystone policies
- Monitor costs daily with alerts across all environments
- Evaluate workload placement based on security, compliance, and cost
- Implement consistent networking across hybrid environments
- Plan for data synchronization and disaster recovery across clouds
Output
- Terraform modules with state management for multi-cloud
- Heat templates for OpenStack infrastructure
- Hybrid architecture diagram (draw.io/mermaid format)
- Cost estimation for monthly spend (public and private cloud)
- Auto-scaling policies and metrics for both environments
- Security groups and network configuration (cloud and OpenStack)
- Hybrid connectivity design (VPN/Direct Connect/ExpressRoute)
- Workload placement strategy matrix
- Data synchronization and backup strategy
- Disaster recovery runbook for hybrid scenarios
- OpenStack cluster sizing recommendations
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.
- 4d ago First seen · 109 lines · 76 tokens per session scan A ec0bb35d23b1
hybrid-cloud-architect is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 903 once invoked, about $0.0004 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
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.
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.
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.
cad-executor-xhigh
The xhigh rung of cad-executor; bin/route.mjs picks it, not the user.
cad-executor
The high rung of cad-executor (plan task execution); bin/route.mjs picks it, not the user.
cad-plan-checker-high
The high rung of cad-plan-checker; bin/route.mjs picks it, not the user.