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/jterratsdev/ableton-live-mcp/devops-toolinggit clone --depth 1 https://github.com/jterratsdev/ableton-live-mcpWhat 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.00992 | $0.00992 |
| Opus 5 | $0.00496 | $0.00496 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
devops-tooling 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Tooling & Operations
DevOps decisions must cover deployability, scalability, downtime strategy, observability, reporting, security, and recovery. Tools are selected by capability, not trend.
Stack by Category
- IaC: Terraform, OpenTofu, Pulumi, CloudFormation, Bicep.
- CI/CD: GitHub Actions, GitLab CI, CircleCI, Buildkite.
- GitOps / Deploy: Argo CD, Flux, Helm, Kustomize.
- Containers / Orchestration: Docker, Kubernetes, ECS/Fargate, Cloud Run.
- Scalability: Kubernetes HPA/VPA, KEDA, autoscaling groups, managed load balancers, CDN.
- Downtime Strategy: rolling deploys, blue-green, canary, dark launch, feature flags with LaunchDarkly, Unleash, or OpenFeature.
- Observability: OpenTelemetry for instrumentation; Prometheus/Grafana for metrics; Loki, ELK, or OpenSearch for logs; Tempo or Jaeger for traces; Datadog, New Relic, or Dynatrace when SaaS is preferred.
- Alerting / On-Call: Alertmanager, PagerDuty, Opsgenie, Grafana OnCall.
- SLO / Error Budgets: Nobl9, Sloth, Pyrra, Grafana SLO, Datadog SLO.
- Infra Reporting / FinOps: Kubecost, OpenCost, Infracost, cloud cost explorers, Grafana dashboards.
- Security DevOps: Trivy, Grype, Snyk, Dependabot, Renovate, Checkov, tfsec, Semgrep, CodeQL.
- Secrets: HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, SOPS with age.
- Backups / DR: Velero, cloud-native backups, database PITR, restore drills.
- Performance / Load Testing: k6, Artillery, Locust, JMeter.
- Synthetic Monitoring: Checkly, Grafana Cloud Synthetic Monitoring, Datadog Synthetics, Playwright scheduled checks.
Operational Design Gates
- Every non-trivial system design must include scalability, downtime, observability, security, cost, and recovery considerations.
- Do not approve infrastructure or release changes without deployment, rollback, monitoring, and ownership details.
- Prefer managed services when they reduce operational risk without creating unacceptable lock-in or cost exposure.
- Record tool choices and major operational trade-offs in an ADR when they affect long-term operations.
- CI/CD, IaC, runbooks, and operational scripts that repeat command matrices, provider lists, environment maps, or resource collections must load the
collection-standardsskill. - Local Docker stacks must publish ports on
127.0.0.1unless the task explicitly requires LAN/public access and Security has accepted the risk. Databases, caches, queues, admin UIs, metrics backends, and Docker socket access are private by default.
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 · 58 lines · 992 tokens per session scan A dab33e0066bb
devops-tooling is a cursor rule published in the GitHub repository jterratsdev/ableton-live-mcp (0 stars, last pushed 8d ago), licensed MIT. It adds 992 tokens to every session, about $0.0050 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.