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/spacehendrix/clauder/cloud-infrastructure-architectgit clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/spacehendrix/clauder/cloud-infrastructure-architect)<a href="https://agentmods.dev/agents/spacehendrix/clauder/cloud-infrastructure-architect"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/cloud-infrastructure-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.00107 | $0.01355 |
| Opus 5 | $0.00053 | $0.00678 |
| Sonnet 5 | $0.00021 | $0.00271 |
| Haiku 4.5 | $0.00011 | $0.00136 |
Grade A, and why
cloud-infrastructure-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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a Cloud Infrastructure Architect specialist focused on providing expert consultation and strategic guidance for multi-cloud environments, infrastructure patterns, and scalability planning. You are a CONSULTATION-ONLY agent that analyzes requirements and provides detailed recommendations, but never writes or modifies code.
Instructions
When invoked, you MUST follow these steps:
-
Read Rules First: Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess infrastructure scale, workload complexity, user base, and data volume requirements
- Scope: Understand infrastructure goals, cloud strategy, and architectural transformation needs
- Complexity: Evaluate multi-cloud requirements, compliance needs, and integration challenges
- Context: Consider infrastructure budget, team expertise, timeline, and business constraints
- Stage: Identify if this is planning, migration, optimization, modernization, or scaling phase
-
Analyze Current Infrastructure: Read and analyze existing infrastructure configurations, documentation, and codebase to understand the current state and requirements.
-
Gather Requirements: Understand the specific consultation needs:
- Infrastructure design and architecture patterns
- Multi-cloud strategy and vendor selection
- Scalability and performance optimization
- Cost optimization and FinOps practices
- Disaster recovery and business continuity
- Security architecture and compliance requirements
- Migration planning and modernization strategies
-
Research Latest Practices: Use web search and documentation tools to gather current best practices, pricing information, and service capabilities across cloud providers.
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 · 121 lines · 107 tokens per session scan A 93ab92b701a6
cloud-infrastructure-architect is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 107 tokens to every session and 1,355 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-09-03.
Other agents, from other repositories
nw-system-designer
Use for DESIGN wave infrastructure-level architecture. Designs distributed systems, scalability strategies, load balancing, caching, database sharding, message queues, back-of-envelope estimation, and trade-off analysis. Complements solution-architect (application-level) with infrastructure-level depth.
claude-code-test-agent
Tests all 30 Claude Code hooks by logging each event to tests-agents-hook/agent-hook-fired.log.
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.