Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jpablo/vibe-types/plugin install vibe-typesWrote 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/jpablo/vibe-types/vibe-clean)<a href="https://agentmods.dev/skills/jpablo/vibe-types/vibe-clean"><img src="https://agentmods.dev/badge/skills/jpablo/vibe-types/vibe-clean.svg" alt="Measured on agentmods" 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.00076 | $0.02271 |
| Opus 5 | $0.00038 | $0.01136 |
| Sonnet 5 | $0.00015 | $0.00454 |
| Haiku 4.5 | $0.00008 | $0.00227 |
Grade A, and why
vibe-types:clean scanned grade A with 0 findings 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 7d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-types:clean — Apply vibe-types knowledge to source files
Skill root:
${CLAUDE_PLUGIN_ROOT}/skills
Refactor source files by applying every relevant technique from the vibe-types
catalog and use-case library. Work through (knowledge-file × source-file) pairs
sequentially, editing files in place with your native tools.
Invocation
/vibe-clean --skill <lang> (--file <path> | --dir <path> | --branch <name>) [OPTIONS]
Exactly one of --file, --dir, or --branch must be given.
Either --skill or --skill-dir must be given.
Arguments
| Flag | Default | Description |
|---|---|---|
--skill <lang> |
— | Language: typescript, python, rust, scala3, lean, haskell, ocaml, java, agda, tlaplus |
--skill-dir <path> |
— | Override: explicit path to skill directory |
--file <path> |
— | Single source file |
--dir <path> |
— | All matching files in directory (recursive) |
--branch <name> |
— | Files changed on this branch vs. merge-base |
--build <cmd> |
none | Shell command to verify after each edit |
--max-retries N |
3 | Fix attempts per build failure |
--commit |
false | Commit after each (knowledge × source) pair |
--only T01,UC03,... |
all | Process only these knowledge IDs |
--dry-run |
false | Print plan without editing |
--consolidate |
false | Final coherence pass after all techniques |
--principles <file> |
built-in | Custom principles file for consolidation |
--base-branch <name> |
main |
Base for --branch diff |
--progress <file> |
.vibe-clean-progress |
Progress tracking file |
Language → file extensions
typescript → .ts .tsx .mts .cts
python → .py
rust → .rs
scala3 → .scala .sc
lean → .lean
haskell → .hs
ocaml → .ml .mli
java → .java
agda → .agda .lagda .lagda.md .lagda.tex
tlaplus → .tla
Step 1 — Resolve skill directory
SKILL_DIR = ${CLAUDE_PLUGIN_ROOT}/skills/<lang>/ # --skill given
SKILL_DIR = <path> # --skill-dir given
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.
- 7d ago First seen · 258 lines · 76 tokens per session scan A bc6fb978e18f
vibe-types:clean is a skill published in the GitHub repository jpablo/vibe-types (43 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 2,271 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.