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 rules/robertsfeir/atelier-pipeline/cloud-architecturegit clone --depth 1 https://github.com/robertsfeir/atelier-pipelineWrote 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/rules/robertsfeir/atelier-pipeline/cloud-architecture)<a href="https://agentmods.dev/rules/robertsfeir/atelier-pipeline/cloud-architecture"><img src="https://agentmods.dev/badge/rules/robertsfeir/atelier-pipeline/cloud-architecture.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.00985 | $0.00985 |
| Opus 5 | $0.00492 | $0.00492 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00098 | $0.00098 |
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 6d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud & Infrastructure Architecture -- Reference
Sarah reads this file when the task involves cloud deployment, Terraform, or infrastructure design. This is NOT loaded for normal application architecture work.
Terraform & IaC
Module Architecture
- One concern per module. Networking, compute, storage, security, monitoring -- separate modules.
- Standard files:
main.tf,variables.tf,outputs.tf,README.md(always),providers.tf,terraform.tf(recommended),backend.tf(root only). - Naming:
terraform-<PROVIDER>-<NAME>. Resources use descriptive names. - Directory: Root module,
modules/for nested,examples/for usage,tests/for Terraform Test files.
Registry & Versions
- Always resolve latest versions from registry. Pin explicitly in ADR.
- Document every provider/module source.
State Management
- Remote state always (S3, GCS, Azure Blob, GitLab-managed, HCP).
- Workspace per environment. Never share state between environments.
- Sensitive values out of Git -- use env vars, CI secrets, or secrets manager.
Security
- Least privilege IAM. No secrets in code/tfvars/comments/outputs.
- State files are sensitive -- remote with access controls.
- Plan before apply. No auto-apply in production.
Formatting (ADR specs)
- 2-space indent, aligned
=signs - Argument order: meta-args -> required -> optional -> nested blocks -> lifecycle
- Variables/outputs alphabetical
- Split by concern:
network.tf,compute.tf,storage.tf, etc.
Testing (stage-appropriate)
- Always:
terraform validate,terraform fmt -check,terraform planin CI. - When mature:
terraform test,tflint,checkov/tfsec. - Examples directory doubles as integration test material.
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.
- 6d ago First seen · 118 lines · 985 tokens per session scan A ee3640c2fb66
cloud-architecture is a cursor rule published in the GitHub repository robertsfeir/atelier-pipeline (25 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 985 tokens to every session, about $0.0049 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.