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/cloudbees-oss/devops-agent-kitWrote 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/cloudbees-oss/devops-agent-kit/devops-patterns)<a href="https://agentmods.dev/rules/cloudbees-oss/devops-agent-kit/devops-patterns"><img src="https://agentmods.dev/badge/rules/cloudbees-oss/devops-agent-kit/devops-patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/cloudbees-oss/devops-agent-kit/devops-patterns"><img src="https://agentmods.dev/badge/rules/cloudbees-oss/devops-agent-kit/devops-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00401 | $0.00401 |
| Opus 5.5 | $0.00160 | $0.00160 |
| Sonnet 5.5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
devops-patterns 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 1mo 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.
What it actually says
DevOps Analysis Patterns
Failure Classification
When triaging a failed CI run, classify the root cause:
| Category | Indicators | Examples |
|---|---|---|
| CONFIG | Validation errors, missing inputs, invalid references | YAML syntax error, missing folder-name input, bad action version |
| CODE | Build/compile/test steps fail after checkout succeeds | Compilation error, test assertion failure, lint violation |
| SECURITY | Security scan step fails | Gitleaks finding, SAST vulnerability, SCA dependency issue |
| ENVIRONMENT | Timeouts, connection errors, resource issues | Runner unavailable, OOM kill, network timeout, disk full |
| KNOWN | Same step + same error pattern as a previous triage | Recurring flaky step, known infrastructure issue |
Security Prioritization
Rank findings by:
- Critical severity (immediate action)
- High severity with approaching SLA deadline
- High severity
- Medium severity
- Low severity
For each finding, always include: finding type, file path, line number, SLA due date.
CI Health Scoring
Calculate a 0-100 score based on:
- Pass rate: 35% weight
- Controller health: 20% weight
- Security posture: 25% weight
- Queue efficiency: 20% weight
Known Quirks
logs_listmay return HTTP 500 — fall back to step names and statusescontrollers_data_getwidgets ci5, ci6, ci7 may return empty — skip gracefullyorganizations_suborg_reportwidgets s4, s5 may return "No Data Found" at org level — use component-level tools instead- Always skip runs with workflow names containing "code_scan" (infrastructure-managed scans)
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.
- 1mo ago First seen · 46 lines · 401 tokens per session scan A 165c82e4e86d
devops-patterns is a cursor rule published in the GitHub repository cloudbees-oss/devops-agent-kit (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 401 tokens to every session, about $0.0016 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .