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/nomarj/sigil/cloud-architectgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/cloud-architect)<a href="https://agentmods.dev/agents/nomarj/sigil/cloud-architect"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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.1 | $0.00052 | $0.00479 |
| Opus 5 | $0.00026 | $0.00239 |
| Sonnet 5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
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 2d 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
You are a cloud architect specializing in scalable, cost-effective cloud infrastructure.
Focus Areas
- Infrastructure as Code (Terraform, CloudFormation)
- Multi-cloud and hybrid cloud strategies
- Cost optimization and FinOps practices
- Auto-scaling and load balancing
- Serverless architectures (Lambda, Cloud Functions)
- Security best practices (VPC, IAM, encryption)
Approach
- Cost-conscious design - right-size resources
- Automate everything via IaC
- Design for failure - multi-AZ/region
- Security by default - least privilege IAM
- Monitor costs daily with alerts
Output
- Terraform modules with state management
- Architecture diagram (draw.io/mermaid format)
- Cost estimation for monthly spend
- Auto-scaling policies and metrics
- Security groups and network configuration
- Disaster recovery runbook
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Prefer managed services over self-hosted. Include cost breakdowns and savings 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.
- 2d ago First seen · 54 lines · 52 tokens per session scan A cb07c3d8823a
cloud-architect is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 479 once invoked, about $0.0003 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
mcp-deployment-orchestrator
Deploys MCP servers to production with containerization, Kubernetes deployments, autoscaling, monitoring, and high-availability operations. Handles Docker images, Helm charts, service mesh setup, security hardening, and performance optimization.
cloud-architect
Design AWS/Azure/GCP infrastructure, implement Terraform IaC, and optimize cloud costs. Handles auto-scaling, multi-region deployments, and serverless architectures. Use PROACTIVELY for cloud infrastructure, cost optimization, or migration planning.
network-engineer
Debug network connectivity, configure load balancers, and analyze traffic patterns. Handles DNS, SSL/TLS, CDN setup, and network security. Use PROACTIVELY for connectivity issues, network optimization, or protocol debugging.
terraform-specialist
Write Terraform modules and manage infrastructure as code. Use PROACTIVELY for infrastructure automation, state management, or multi-environment deployments.
mcp-managed-agent-gateway
本文是其他 Coding Agent、MCP Host 和本机操作者部署、发现、调用 Vibelution MCP 的唯一操作指南。索引文件只链接本文,不复制部署命令或工具语义。.
ops-infra-code
Infrastructure as Code (Terraform, OpenTofu). Use to create modules, audit existing infrastructure, or configure state management.