consumer-regression-suite SKILL.md skillB
consumer-regression-suite from pisberg/vibetags is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pisberg/vibetags/consumer-regression-suite@git:20261006.c416addPins git:20261006.c416add in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pisberg/vibetags
- Path
.claude/skills/consumer-regression-suite/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261006.c416add, committed Oct 6, 2026
- First version recorded
- Sep 17, 2026
- Size
- 10,869 bytes
- Repository stars
- 25
- License
- MIT
Build every downstream consumer of VibeTags against a chosen VibeTags version and report which ones actually pass. Use when the user says "regression suite", "consumer sweep", "test the consumers", "check the downstream repos", "does the new version break anything", or before cutting a VibeTags release.
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
# Consumer regression suite VibeTags' own test suite says the processor works. It says nothing about whether a real consumer still builds. This skill answers that second question, for every Java repo under `../` that depends on VibeTags. The executable core is `tools/consumer-sweep.sh` in this repo. This document is the judgement around it: what to run, what a result means, and what not to believe. ## Step 1 — Decide which VibeTags the sweep is testing Two different questions, and they need different setups. Ask which one is wanted if it is not obvious from the request. **"Does the released version still work?"** Use the published version directly. Nothing to install; consumers resolve it from Maven Central. **"Does what we are about to release still work?"** `main` is usually ahead of the newest tag, so the published artifact is not the code under test. Check first: ```bash git -C <vibetags> log "$(git -C <vibetags> tag --sort=-v:refname | head -1)"..main --oneline ``` If that is non-empty, build and install `main` locally: ```bash cd vibetags-annotations && mvn install -DskipTests cd ../vibetags && mvn install -DskipTests cd ../vibetags-bom && mvn install …
Read the whole file at its exact version.
How to install
mdr add pisberg/vibetags/consumer-regression-suite@sha256:b207af85b8eec470The line at the top of this page pins the label git:20261006.c416add, 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_wzqjdtteraujawyh)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Sep 17, 2026 and Oct 6, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.c416add latest | 2026-10-06 | c416add | 10,869 B | B | view · diff |
| git:20260925.30f298f | 2026-09-25 | 30f298f | 10,869 B | B | view · diff |
| git:20260922.d909164 | 2026-09-22 | d909164 | 10,606 B | B | view · diff |
| git:20260922.71ae16a | 2026-09-22 | 71ae16a | 9,978 B | B | view · diff |
| git:20260921.72ea14c | 2026-09-21 | 72ea14c | 9,348 B | B | view · diff |
| git:20260917.538088a | 2026-09-17 | 538088a | 8,569 B | B | view · diff |
| git:20260917.ce981a6 | 2026-09-17 | ce981a6 | 8,459 B | B | view |
Audit of the latest version
- fail: No recursive delete of root, home or parent (matched: rm -rf ~/)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10869 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
pisberg/vibetags · 25 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wzqjdtteraujawyh GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/consumer-regression-suite GET https://markdownregistry.com/api/v1/blob/b207af85b8eec470da78a872931cb8dad62edb689ae7aa085d699597543c790a
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.