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/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/vibes-plug-devops)<a href="https://agentmods.dev/rules/roedyrustam/vibes-plug/vibes-plug-devops"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/vibes-plug-devops/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/roedyrustam/vibes-plug/vibes-plug-devops"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/vibes-plug-devops.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.00294 |
| Opus 5.5 | $0.00000 | $0.00118 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
vibes-plug-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 today.
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
Vibes-Plug Cloud & DevOps Platform Engineering (2026 Edition)
When editing Dockerfiles, container manifests, CI/CD pipelines, or deployment configurations, Cursor AI MUST enforce these standards:
1. Container Hardening
- Multi-Stage BuildKit: Separate build dependencies from production runtime to minimize container image surface area.
- Rootless & Distroless: Never run production containers as
root. Always use non-root user (USER nonroot:nonrootorUSER node) and distroless/alpine base images. - Clean Secrets: Never hardcode secrets, tokens, or private keys in Dockerfiles or compose files. Mount secrets via BuildKit (
--mount=type=secret).
2. CI/CD & Supply Chain Security
- OIDC Cloud Auth: Prefer GitHub Actions OIDC federation over static long-lived cloud credentials.
- Pinning: Pin GitHub Actions and container base images with immutable SHA-256 digests.
- SBOM & Attestation: Generate CycloneDX SBOM during release workflows and verify provenance.
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.
- today First seen · 20 lines · 0 tokens per session scan A 12639ce7fac8
vibes-plug-devops is a cursor rule published in the GitHub repository roedyrustam/vibes-plug (114 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 294 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-10-27.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.