rea-ci-tests-audit SKILL.md skillA
rea-ci-tests-audit from roedyrustam/vibes-plug is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add roedyrustam/vibes-plug/rea-ci-tests-audit@v4.8.0Pins v4.8.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- roedyrustam/vibes-plug
- Path
.cursor/skills/rea-ci-tests-audit/SKILL.md- Versions recorded
- 2
- Latest version
- v4.8.0, committed Nov 14, 2026
- First version recorded
- Nov 5, 2026
- Size
- 18,707 bytes
- Repository stars
- 126
- License
- MIT
Audit REA CI and test suites for correctness and measured performance / Audit suite tes dan CI REA untuk ketepatan dan performa terukur.
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
# REA CI and tests audit Establish which checks still catch real regressions and which costs can be removed without losing that protection. The outcome may be a verified fix, an evidence-backed recommendation, or an explicit decision to stop. Follow the checkout's `AGENTS.md`, [testing guide](../../../docs/testing.md), and [contribution rules](../../../CONTRIBUTING.md). Use their current commands and pinned toolchain, rather than commands remembered from an earlier audit. Preserve the requested scope: investigation alone does not authorize edits; this skill does not grant permission to publish issues, push, or merge. Existing user authorization still applies. Keep audit notes and raw results outside the tracked tree, normally in a task-specific `/tmp` directory. ## Hard Guardrails (Declarative Invariants) - **Pin Baseline Revision & Isolated Worktree**: Always record the exact git commit SHA, toolchain version, and command arguments before running a CI audit; never mutate another task's working directory. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5jlixrac65lu2wow/e078375167157807bbf94c18ec322a01bbe25ffe8caeb106afaf7807736d56d0.json
Then /plugin install rea-ci-tests-audit@markdownregistry-5jlixrac65lu2wow in Claude Code. It installs v4.8.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add roedyrustam/vibes-plug/rea-ci-tests-audit@sha256:e078375167157807The line at the top of this page pins the label v4.8.0, 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_5jlixrac65lu2wow)
1 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/rea-ci-tests-audit 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 rea-ci-tests-audit from somewhere else? Ask it: where did my rea-ci-tests-audit 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 2 versions of this file, between Nov 5, 2026 and Nov 14, 2026, about one every 9 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v4.8.0 latest | 2026-11-14 | a68dd5d | 18,707 B | A | view · diff |
| v4.7.0 | 2026-11-05 | 565d308 | 12,947 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/rea-ci-tests-audit/SKILL.md? 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: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (18707 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_5jlixrac65lu2wow GET https://markdownregistry.com/api/v1/resolve?ref=roedyrustam/vibes-plug/rea-ci-tests-audit GET https://markdownregistry.com/api/v1/blob/e078375167157807bbf94c18ec322a01bbe25ffe8caeb106afaf7807736d56d0
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: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from roedyrustam/vibes-plug
Every file in roedyrustam/vibes-plug
Other files named rea-ci-tests-audit
Browse by kind, by grade A, or by owner.
Kept in .cursor/skills, the folder Cursor reads. More agent skills for Cursor.