vibetags-usage SKILL.md skillA

vibetags-usage from pisberg/vibetags is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add pisberg/vibetags/vibetags-usage@v1.4.2

Pins v1.4.2 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
pisberg/vibetags
Path
.claude/skills/vibetags-usage/SKILL.md
Versions recorded
15
Latest version
v1.4.2, committed Nov 15, 2026
First version recorded
Sep 14, 2026
Size
23,785 bytes
Repository stars
25
License
MIT

This skill should be used when the user asks how to use VibeTags, add or choose an `@AI*` guardrail annotation (`@AILocked`, `@AIContext`, `@AIPrivacy`, `@AIAudit` or any other from `se.deversity.vibetags`), opt a project into AI platform files, protect code from AI edits, or find out why a guardrail file was not generated.

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

# VibeTags Usage Guide

VibeTags is a **compile-time Java annotation processor** that generates AI platform-specific guardrail files from source annotations. Zero runtime overhead — all annotations have `RetentionPolicy.SOURCE`.

## Quick Setup

### 1. Add the two artifacts

VibeTags ships as **two** artifacts and you need both. Depending on only one of them is the most
common "VibeTags is broken" report, and neither failure produces a useful error:

| Artifact | Belongs on | Gives you | If you omit it |
|---|---|---|---|
| `vibetags-annotations` | the **compile** classpath | the 44 `@AI*` annotation types you write in source | `cannot find symbol` on every `@AI*` |
| `vibetags-processor` | the **annotation-processor** path | the processor that reads them and writes the guardrail files | compiles green, generates nothing |

**Maven**. Annotations as an ordinary dependency, processor on `annotationProcessorPaths`:

```xml
<dependencies>
    <dependency>
        <groupId>se.deversity.vibetags</groupId>
        <artifactId>vibetags-annotations</artifactId>
        <version>1.4.2</version>
    </dependency>
</dependencies>

<build>
    <plugins>
        <plugin>
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xvgdokqhmd54nfit/d19c8af877f5f2ab3790d018c9cb2aa4cb57ba1a94b1ae212bcebe4c5c0008f5.json

Then /plugin install vibetags-usage@markdownregistry-xvgdokqhmd54nfit in Claude Code. It installs v1.4.2, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add pisberg/vibetags/vibetags-usage@sha256:d19c8af877f5f2ab

The line at the top of this page pins the label v1.4.2, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_xvgdokqhmd54nfit.svg)](https://markdownregistry.com/a/art_xvgdokqhmd54nfit)

3 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in pisberg/vibetags/vibetags-usage 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 vibetags-usage from somewhere else? Ask it: where did my vibetags-usage 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 15 versions of this file, between Sep 14, 2026 and Nov 15, 2026, about one every 4 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v1.4.2 latest2026-11-15 d39e80e 23,785 BA view · diff
v1.4.22026-11-14 9796ac4 23,767 BA view · diff
v1.4.12026-10-24 12d3214 23,767 BA view · diff
v1.4.02026-10-19 6d5a92b 23,767 BA view · diff
v1.4.02026-10-08 7413a9a 23,427 BA view · diff
v1.3.82026-10-06 495c058 23,427 BA view · diff
v1.3.82026-10-06 58e3e31 24,546 BA view · diff
v1.3.82026-10-05 5ef290e 24,801 BA view · diff
v1.3.82026-09-28 149677c 24,739 BA view · diff
v1.3.72026-09-25 1db7b54 24,739 BA view · diff
v1.3.62026-09-21 9d3346d 24,739 BA view · diff
v1.3.52026-09-20 e596793 24,739 BA view · diff
v1.3.52026-09-19 0d98a54 24,608 BA view · diff
v1.3.52026-09-19 25000fc 24,551 BA view · diff
v1.3.52026-09-14 260a21f 86,544 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (23785 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

GitHub

pisberg/vibetags · 25 stars · license MIT · pushed 2026-11-18 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_xvgdokqhmd54nfit
GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/vibetags-usage
GET https://markdownregistry.com/api/v1/blob/d19c8af877f5f2ab3790d018c9cb2aa4cb57ba1a94b1ae212bcebe4c5c0008f5

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 pisberg/vibetags

add-annotation SKILL.md skill
pisberg/vibetags · .claude/skills/add-annotation/SKILL.md · Add a new @AI... guardrail annotation to VibeTags — register it in GuardrailAnnotations, then wire it through every…
git:20261006.495c058 · audit A · 25 stars
add-platform SKILL.md skill
pisberg/vibetags · .claude/skills/add-platform/SKILL.md · Add support for a new AI coding tool, IDE, PR-reviewer, or context-packer to VibeTags — wire a new generated output…
git:20261009.e001c8d · audit A · 25 stars
bump-dependencies SKILL.md skill
pisberg/vibetags · .claude/skills/bump-dependencies/SKILL.md · Bump every third-party dependency, plugin and toolchain pin in VibeTags to its latest stable release, mirror the pins…
git:20261105.eb1c69f · audit A · 25 stars
consultation-loop SKILL.md skill
pisberg/vibetags · .claude/skills/consultation-loop/SKILL.md · Pre-push adversarial interrogation of the current branch's diff by a fresh reviewer with no memory of writing it - five…
git:20260815.32e6c75 · audit A · 25 stars
consumer-regression-suite SKILL.md skill
pisberg/vibetags · .claude/skills/consumer-regression-suite/SKILL.md · Build every downstream consumer of VibeTags against a chosen VibeTags version and report which ones actually pass. Use…
git:20261006.c416add · audit B · 25 stars
correctness-hunt SKILL.md skill
pisberg/vibetags · .claude/skills/correctness-hunt/SKILL.md · Run a bug hunt against this repository under a fixed work order - baseline the suite, hunt with named bug-shape lenses…
git:20260815.32e6c75 · audit A · 25 stars
load-tests SKILL.md skill
pisberg/vibetags · .claude/skills/load-tests/SKILL.md · Run the VibeTags benchmark harness in load-tests/ and report the numbers honestly — annotation-volume and memory…
git:20260926.c4dbb2c · audit A · 25 stars
release SKILL.md skill
pisberg/vibetags · .claude/skills/release/SKILL.md · Cut a new VibeTags release — bump the version everywhere, update the CHANGELOG, open the release PR, and create the…
git:20261117.b0c62bd · audit A · 25 stars
speckit-analyze SKILL.md skill
pisberg/vibetags · .claude/skills/speckit-analyze/SKILL.md · Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after…
git:20260920.e596793 · audit A · 25 stars
speckit-checklist SKILL.md skill
pisberg/vibetags · .claude/skills/speckit-checklist/SKILL.md · Generate a custom checklist for the current feature based on user requirements.
git:20260920.e596793 · audit A · 25 stars
speckit-clarify SKILL.md skill
pisberg/vibetags · .claude/skills/speckit-clarify/SKILL.md · Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and…
git:20260920.e596793 · audit A · 25 stars
speckit-constitution SKILL.md skill
pisberg/vibetags · .claude/skills/speckit-constitution/SKILL.md · Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent…
git:20260920.e596793 · audit A · 25 stars

Every file in pisberg/vibetags

Other files named vibetags-usage

vibetags-usage SKILL.md skill
pisberg/skill3 · .claude/skills/vibetags-usage/SKILL.md · This skill should be used when the user asks how to "use VibeTags", "add VibeTags annotations", "set up AI guardrails"…
v1.0.0-RC1 · audit A · 6 stars

Browse by kind, by grade A, or by owner.