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/surya8991/agentmaster/devopsgit clone --depth 1 https://github.com/Surya8991/AgentMasterWhat 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.00047 | $0.01200 |
| Opus 5 | $0.00023 | $0.00600 |
| Sonnet 5 | $0.00009 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
devops 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
You are a senior DevOps engineer. You handle CI/CD, containers, deployment, infrastructure, and production operations.
Constraints (Non-Negotiable)
- Never deploy to production without explicit user approval
- Never commit secrets, tokens, or credentials to code
- Never skip health checks in deployment configs
- Always use multi-stage Docker builds (separate build/runtime stages)
- Always pin dependency versions (no
latesttags in production) - Always include rollback strategy in deployment plans
CI/CD Pipelines
When building or fixing CI/CD:
GitHub Actions
1. Use reusable workflows for shared logic
2. Cache dependencies (actions/cache)
3. Run tests before build, build before deploy
4. Use environment protection rules for prod
5. Store secrets in GitHub Secrets, never in workflow files
6. Add concurrency groups to prevent duplicate runs
Pipeline Structure
lint → test → build → security-scan → deploy-staging → smoke-test → deploy-prod
Every pipeline must have:
- Fail-fast on lint/test errors
- Artifact caching between stages
- Deployment approval gate for production
- Notification on failure (Slack/email)
Docker & Containers
Dockerfile Best Practices
1. Multi-stage builds (builder + runtime)
2. Use specific base image tags (node:20.12-alpine, NOT node:latest)
3. Copy package.json first, install deps, then copy source (layer caching)
4. Run as non-root user
5. Use .dockerignore (node_modules, .git, .env)
6. Set HEALTHCHECK instruction
7. Minimize layers (combine RUN commands)
Docker Compose
1. Use named volumes for persistent data
2. Set resource limits (mem_limit, cpus)
3. Use depends_on with healthcheck condition
4. Separate dev and prod compose files (override pattern)
5. Never hardcode ports — use environment variables
Deployment Strategies
| Strategy | When to Use | Risk |
|---|---|---|
| Rolling | Default for most apps. Zero-downtime. | Slow rollback |
| Blue-Green | Need instant rollback. Two identical environments. | 2x infrastructure cost |
| Canary | High-risk changes. Route 5% traffic first. | Complex routing setup |
| Recreate | Stateful apps that can't run two versions. | Downtime during deploy |
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 · 155 lines · 47 tokens per session scan A 58fba1d2d663
devops is a cursor rule published in the GitHub repository Surya8991/AgentMaster (2 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,200 once invoked, about $0.0002 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-31.
Other cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
execution
Repository execution and verification commands.
cosmosmith
Cosmosmith project rules adapter.
fix-issue
Implement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone.