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.
git clone --depth 1 https://github.com/madebyaris/advance-minimax-m3-cursor-rulesWrote 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/madebyaris/advance-minimax-m3-cursor-rules/devops-infrastructure)<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/devops-infrastructure"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/devops-infrastructure.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.00000 | $0.01098 |
| Opus 5 | $0.00000 | $0.00549 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
devops-infrastructure 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps & Infrastructure Patterns
Mechanical reference for containerization, orchestration, IaC, and CI/CD. For general coding workflow (read-before-edit, minimal diff, verification labels), the always-on core Code Discipline and App And Scaffold Discipline sections are canonical.
Load this rule when touching infrastructure files matched by globs. For unfamiliar provider APIs or version-sensitive changes, verify against current official docs (or use the deep-research skill) — do not invent flags, resource names, or provider syntax.
Before Changing Infrastructure
- Read existing Docker, compose, k8s, Terraform, Helm, and CI workflow files in this repo first.
- Note pinned base images, provider versions, and environment naming — match them unless the task requires a deliberate upgrade.
- Identify blast radius: prod deploy, secrets, stateful resources, and rollback path.
- Prefer plan / dry-run / validate before apply / deploy / push.
Validate Before Apply
| Tool | Smallest useful check |
|---|---|
| Docker | docker build -t test:local . |
| Compose | docker compose config |
| Kubernetes | kubectl apply --dry-run=client -f … or kubectl diff -f … |
| Terraform | terraform fmt -check, terraform validate, terraform plan |
| Helm | helm lint, helm template (render locally) |
| GitHub Actions | YAML syntax + action pin review; run workflow on a branch when safe |
Never recommend terraform apply, kubectl apply, or production deploy without a plan/dry-run step unless the user explicitly skips it.
Decision Quick Reference
| Need | Prefer |
|---|---|
| Local dev stack | Docker Compose when sufficient; k8s only when repo already uses it |
| Secrets | Platform secret stores / CI secrets — never commit plaintext |
| CI | Extend existing workflow patterns in .github/workflows/ rather than inventing a parallel pipeline |
| Image tags | Pin major.minor (or digest); avoid :latest in anything that ships |
| Terraform state | Remote backend + locking when team/shared; do not hand-edit state |
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 · 99 lines · 0 tokens per session scan A dc39c950880f
devops-infrastructure is a cursor rule published in the GitHub repository madebyaris/advance-minimax-m3-cursor-rules (125 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,098 tokens. 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
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
docker
Docker: multi-stage builds, security, compose.
fix-bugs
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description.
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
learnship
Activate learnship agentic engineering workflows — structured phases, persistent memory, learning partner, and impeccable UI design. Use whenever a user is working on a software project or asks about project planning, phases, workflows, or how to build something.
behavior-principles
Global behavioral principles for all AI-assisted work in this repository. Covers thinking before coding, simplicity, surgical changes, goal-driven execution, and communication standards.