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/jakerains/CitrusRulesWrote 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/jakerains/citrusrules/devops-ci-cd)<a href="https://agentmods.dev/rules/jakerains/citrusrules/devops-ci-cd"><img src="https://agentmods.dev/badge/rules/jakerains/citrusrules/devops-ci-cd/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/jakerains/citrusrules/devops-ci-cd"><img src="https://agentmods.dev/badge/rules/jakerains/citrusrules/devops-ci-cd.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.00000 | $0.00242 |
| Opus 5.5 | $0.00000 | $0.00097 |
| Sonnet 5.5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
devops-ci-cd 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 2mo 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
name: DevOpsCiCdStandards type: Auto Attached description: Standardize build, test, and deployment pipelines glob: **/*.{yml,yaml} priority: high
DevOps CI/CD Standards
Automate testing and deployment for all projects.
Pipeline Basics
- Run linting and tests on every commit.
- Use caching to speed up builds.
- Fail fast when steps exit with an error.
Deployment
- Use environment specific configuration files.
- Tag releases and maintain changelogs.
- Roll back automatically on failed deployments.
Security and Monitoring
- Store secrets in a secure vault.
- Scan dependencies for vulnerabilities.
- Monitor pipelines for unusual activity.
# Example GitHub Actions snippet
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npm test
These rules help maintain stable and observable delivery pipelines.
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.
- 2mo ago First seen · 48 lines · 0 tokens per session scan A 297d9fcfd06f
devops-ci-cd is a cursor rule published in the GitHub repository jakerains/CitrusRules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 242 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-31.
Other cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
vibes-plug-devops
Vibes-Plug Cloud & DevOps Platform Engineering — Docker BuildKit, distroless runtimes, Kubernetes GitOps, and GitHub Actions OIDC.
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
verification-evidence
Requires evidence, not assertions, before a change is called done, and points to the per-repo verification contract. Always-applied behavioral rule.
cursor-asdd
ASDD contribution rules for this repository.
agents
Agent engineering standards — Agents (TR-SEC-003).