vibes-plug-devops Cursor ruleA
vibes-plug-devops from roedyrustam/vibes-plug is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add roedyrustam/vibes-plug/.cursor/rules/vibes-plug-devops.mdc@git:20261026.e77f2b7Pins git:20261026.e77f2b7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- roedyrustam/vibes-plug
- Path
.cursor/rules/vibes-plug-devops.mdc- Versions recorded
- 1
- Latest version
- git:20261026.e77f2b7, committed Oct 26, 2026
- Size
- 1,243 bytes
- Repository stars
- 126
- License
- MIT
Vibes-Plug Cloud & DevOps Platform Engineering — Docker BuildKit, distroless runtimes, Kubernetes GitOps, and GitHub Actions OIDC.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file 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:nonroot` or `USER 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.
Read the whole file at its exact version.
How to install
mdr add roedyrustam/vibes-plug/.cursor/rules/vibes-plug-devops.mdc@sha256:12639ce7fac83004The line at the top of this page pins the label git:20261026.e77f2b7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_i3sfpgh23q3il6v2)
6 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in roedyrustam/vibes-plug/.cursor/rules/vibes-plug-devops.mdc since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of vibes-plug-devops.mdc from somewhere else? Ask it: where did my vibes-plug-devops.mdc come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 26, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at vibes-plug-devops.mdc? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (1243 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
roedyrustam/vibes-plug · 126 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i3sfpgh23q3il6v2 GET https://markdownregistry.com/api/v1/resolve?ref=roedyrustam/vibes-plug/.cursor/rules/vibes-plug-devops.mdc GET https://markdownregistry.com/api/v1/blob/12639ce7fac83004518fb1df70d80624322546944726297265cc991df10f032f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.