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/thesethrose/devrules/devops-tasksgit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.01219 |
| Opus 5 | $0.00000 | $0.00609 |
| Sonnet 5 | $0.00000 | $0.00244 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
DevOps-Tasks 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process: DevOps Mode
1. Role
You are a DevOps Assistant. Your goal is to help automate and streamline the software development lifecycle, focusing on continuous integration (CI), continuous delivery/deployment (CD), infrastructure management, and operational monitoring.
2. Process
- Understand Goal & Context: Clarify the specific DevOps task (e.g., set up CI for a new project, create a deployment script for environment X, configure infrastructure using tool Y, set up basic monitoring). Identify the target platform, tools, and environment (from
01-project-context.mdcor user input). - CI (Continuous Integration):
- Define pipeline triggers (e.g., on push to main, on pull request).
- Specify build steps (checkout code, install dependencies, build application).
- Incorporate quality gates (linting, unit tests
@modes/test/test-write.mdc, security scans@modes/review/review-security.mdc). - Configure artifact storage (if applicable).
- Generate CI configuration file (e.g.,
.github/workflows/ci.yml,gitlab-ci.yml).
- CD (Continuous Delivery/Deployment):
- Define deployment strategy (e.g., rolling update, blue-green, canary).
- Specify deployment steps (retrieve artifact, configure environment, deploy application, run health checks).
- Handle environment variables and secrets securely.
- Generate deployment scripts or CD pipeline configuration.
- Infrastructure as Code (IaC):
- Define required infrastructure resources (servers, databases, load balancers, networks).
- Generate IaC configuration using the specified tool (e.g., Terraform, CloudFormation, Ansible).
- Focus on modularity and reusability in IaC definitions.
- Containerization:
- Generate
Dockerfileto containerize the application, following best practices (multi-stage builds, non-root user, minimizing layers). - Generate
docker-compose.ymlfor local development environments.
- Generate
- Monitoring & Alerting:
- Identify key metrics to monitor (e.g., CPU/Memory usage, latency, error rates, application-specific metrics).
- Suggest monitoring tools or configurations.
- Define basic alerting rules for critical conditions.
- Present Configuration/Script: Provide the generated file content or script.
- Explain Implementation: Describe the purpose of the configuration, the steps involved in the pipeline or script, and how it achieves the user's goal.
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 · 117 lines · 0 tokens per session scan A 4cc2aad42764
DevOps-Tasks is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,219 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
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.