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/madebyaris/rakitui-ai/devops-infrastructuregit clone --depth 1 https://github.com/madebyaris/rakitui-aiWhat 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.00000 | $0.04736 |
| Opus 5 | $0.00000 | $0.02368 |
| Sonnet 5 | $0.00000 | $0.00947 |
| Haiku 4.5 | $0.00000 | $0.00474 |
Grade B, and why
devops-infrastructure scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# Never run as root Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
CMD wget --no-verbose --tries=1 --spider http://localhost:3000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 914 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps & Infrastructure Patterns
Containerization, orchestration, infrastructure as code, and CI/CD best practices.
CRITICAL: Agentic-First DevOps
Pre-Development Verification (MANDATORY)
Before writing ANY DevOps configuration:
1. CHECK TOOL AVAILABILITY
→ run_terminal_cmd("docker --version")
→ run_terminal_cmd("kubectl version --client")
→ run_terminal_cmd("terraform --version")
→ run_terminal_cmd("helm version")
2. VERIFY CURRENT VERSIONS (use web_search)
→ web_search("Terraform latest version December 2024")
→ web_search("Kubernetes latest stable version 2024")
→ web_search("Docker best practices 2024")
3. CHECK EXISTING INFRASTRUCTURE
→ Read existing Dockerfile, docker-compose.yml, *.tf files
→ Understand current state before modifying
→ Check terraform.tfstate or remote state
4. VALIDATE CONFIGURATIONS BEFORE APPLYING
→ terraform validate
→ docker-compose config
→ kubectl apply --dry-run=client
CLI-First DevOps Workflow
ALWAYS use CLI for validation:
# Docker
docker build -t test:latest .
docker-compose config # Validate compose file
docker-compose up --dry-run # Test without running
# Kubernetes
kubectl apply --dry-run=client -f manifest.yaml
kubectl diff -f manifest.yaml # See changes before applying
kubeval manifest.yaml # Validate against schema
# Terraform
terraform init
terraform fmt -recursive
terraform validate
terraform plan -out=tfplan # ALWAYS plan before apply
# Helm
helm lint ./my-chart
helm template ./my-chart # Render templates locally
helm install --dry-run --debug my-release ./my-chart
Post-Edit Verification
After ANY infrastructure code changes:
# Docker
docker build --no-cache -t test:latest .
docker run --rm test:latest echo "Build verified"
# Terraform
terraform fmt -check -recursive
terraform validate
terraform plan
# Kubernetes
kubectl apply --dry-run=server -f . # Server-side validation
kubectl get events --sort-by='.lastTimestamp' # Check for issues
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 · 914 lines · 0 tokens per session scan B e3ba8bcb273f
devops-infrastructure is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,736 tokens. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
cursorrules
You are a senior platform engineer working in production-first environments. Apply platform engineering best practices for Kubernetes, Terraform, GitOps, GitHub Actions, AWS, Azure, Helm, Kyverno, OPA/Conftest, observability, and PR review.
devops-infrastructure
DevOps and infrastructure: Docker, Kubernetes, Terraform, CI/CD. Load when editing Dockerfiles, compose, k8s manifests, Terraform, or workflow YAML — not for application code.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
cursorrules
Read and follow CLAUDE.md in the repository root before making any changes. It contains all agent rules for this project.
cursorrules
When the user asks about ci cd generator, use ci-cd-generator-ai-mcp tools: generatepipeline, validateconfig, listtemplates, optimizestages.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.