Borrowing it
Nothing to install: this file belongs to PIsberg/vibetags. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PIsberg/vibetags/main/.claude/skills/consumer-regression-suite/SKILL.mdgit clone --depth 1 https://github.com/PIsberg/vibetagsWrote 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/skills/pisberg/vibetags/consumer-regression-suite)<a href="https://agentmods.dev/skills/pisberg/vibetags/consumer-regression-suite"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/consumer-regression-suite/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/skills/pisberg/vibetags/consumer-regression-suite"><img src="https://agentmods.dev/badge/skills/pisberg/vibetags/consumer-regression-suite.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.00069 | $0.01975 |
| Opus 5 | $0.00034 | $0.00988 |
| Sonnet 5 | $0.00014 | $0.00395 |
| Haiku 4.5 | $0.00007 | $0.00198 |
Grade C, and why
consumer-regression-suite scanned grade C with 1 finding 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.m2/repository/se/deversity/vibetags/*/<version> How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consumer regression suite
VibeTags' own 1537 tests say the processor works. They say 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:
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:
cd vibetags-annotations && mvn install -DskipTests
cd ../vibetags && mvn install -DskipTests
cd ../vibetags-bom && mvn install
Installing main under a version number that is also on Central makes the local copy differ
from the published one for every later build on this machine. Say so, and offer the cleanup
in Step 5. Installing under a fresh -SNAPSHOT avoids it but means no consumer PR can pin
the result.
Step 2 — Run the sweep
bash tools/consumer-sweep.sh <version> # every consumer
bash tools/consumer-sweep.sh <version> blindbean # one
Per repo it fetches, branches off origin/main, rewrites every place that repo declares the
VibeTags version, builds with the repo's own wrapper, and prints the build's real exit code.
It commits nothing, pushes nothing and opens nothing.
Consumers, and how each declares the version:
| repo | build | declares the version in |
|---|---|---|
blindbean |
Maven (mvnw) |
pom.xml |
codekarta |
Maven + Gradle | pom.xml and build.gradle.kts — both, kept in sync |
common-license-lib |
Maven + Gradle | pom.xml and build.gradle.kts |
skill3 |
Gradle | build.gradle |
async-test-lib |
Maven + Gradle | pom.xml only; Gradle reads it from the POM |
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.
- 11d ago First seen · 151 lines · 69 tokens per session scan C b1c41c08b153
consumer-regression-suite is a skill published in the GitHub repository PIsberg/vibetags (15 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 1,975 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
056-design-avoid-breaking-changes
Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review…
spring-to-solon-skill
Expert guidance for migrating Java projects from Spring Boot / Spring Cloud to the Solon framework. Provides annotation mapping, dependency replacement, architecture differences, and step-by-step migration for IoC, Web, Data, Security, Scheduling, Validation, Cloud, and Testing. Use when migrating Spring Boot/Cloud…
develop-inspection-feature
End-to-end workflow for adding a new inspection or quick-fix feature to the explyt/spring-plugin repository: duplicate check, fact verification against authoritative javadoc, base-class and gating choice (isAvailableForFile), visible-element highlighting, registration, platform tests, branch and PR. Use when the user…
alpha-forge-preship
Alpha Forge quality gates for PR review - RNG determinism, URL validation, parameter validation, manifest sync.
cgs-propagate-design-change
Use for propagate design change tasks that trace a design change through systems, docs, tasks, tests, content, and release risk; produce verification evidence, changed or proposed files, and handoff boundaries.
improve-test-coverage
Iteratively write .NET unit tests to improve code coverage toward 80% line and branch targets. USE FOR: autonomously running tests, finding gaps, writing targeted tests, and repeating until 80% coverage or plateau. Calls all 7 dotnet-coverage-mcp MCP tools: GetSourceFiles, RunTestsWithCoverage, GetCoverageSummary…