A code audit for patterns associated with unreviewed AI-generated code, sometimes called vibe coding. It produces a scored report with specific findings and suggested fixes.

Use it to inspect a file, directory, Git diff, recent commits, or staged changes, with optional fix suggestions and a saved Markdown report.

It helps identify code that may have been accepted without enough human checking, so quality and maintainability problems are easier to address.

vibe-check — Skill for Claude Code and Codex by cacheforge-ai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add cacheforge-ai/cacheforge-skills --skill vibe-check

Clone the repo

git clone --depth 1 https://github.com/cacheforge-ai/cacheforge-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/vibe-check/github.svg)](https://agentmods.dev/skills/cacheforge-ai/cacheforge-skills/vibe-check)

Your own site

<a href="https://agentmods.dev/skills/cacheforge-ai/cacheforge-skills/vibe-check"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/vibe-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cacheforge-ai/cacheforge-skills/vibe-check"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/vibe-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,332 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00036	$0.01332
Opus 5.5	$0.00014	$0.00533
Sonnet 5.5	$0.00007	$0.00266
Haiku 4.5	$0.00004	$0.00133

Measured 1mo ago against content hash 41c98f0e6c95, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibe-check 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 1mo ago.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/analyze.sh, scripts/common.sh, scripts/git-diff.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/vibe-check/SKILL.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🎭 Vibe Check

Audit code for "vibe coding" — AI-generated code accepted without proper human review. Get a scored report card with specific findings and fix suggestions.

Trigger

Activate when the user mentions any of:

"vibe check"
"vibe-check"
"audit code"
"code quality"
"vibe score"
"check my code"
"review this code for vibe coding"
"code review"
"vibe audit"

Instructions

1. Determine the Target

Ask the user what code to analyze. Accepted inputs:

Single file: app.py, src/utils.ts
Directory: src/, ., my-project/
Git diff: last N commits, staged changes, or branch comparison

2. Run the Analysis

# Single file or directory
bash "$SKILL_DIR/scripts/vibe-check.sh" TARGET

# With fix suggestions
bash "$SKILL_DIR/scripts/vibe-check.sh" --fix TARGET

# Git diff (last 3 commits)
bash "$SKILL_DIR/scripts/vibe-check.sh" --diff HEAD~3

# Staged changes with fixes
bash "$SKILL_DIR/scripts/vibe-check.sh" --staged --fix

# Save to file
bash "$SKILL_DIR/scripts/vibe-check.sh" --fix --output report.md TARGET

3. Present the Report

The output is a Markdown report. Present it directly — it's designed to be screenshot-worthy.

Discord v2 Delivery Mode (OpenClaw v2026.2.14+)

When the conversation is happening in a Discord channel:

Send a compact summary first (grade, score, file count, top 3 findings), then ask if the user wants the full report.
Keep the first message under ~1200 characters and avoid wide Markdown tables in the first response.
If Discord components are available, include quick actions:
- Show Top Findings
- Show Fix Suggestions
- Run Diff Mode
If components are not available, provide the same follow-ups as a numbered list.
Prefer short follow-up chunks (<=15 lines per message) when sending the full report.

Quick Reference

Command	Description
`vibe-check FILE`	Analyze a single file
`vibe-check DIR`	Scan directory recursively
`vibe-check --diff`	Check last commit's changes
`vibe-check --diff HEAD~5`	Check last 5 commits
`vibe-check --staged`	Check staged changes
`vibe-check --fix DIR`	Include fix suggestions
`vibe-check --output report.md DIR`	Save report to file

Read the full file on GitHub · 155 lines

Files

What ships with it

12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

1mo ago First seen · 155 lines · 36 tokens per session scan A 41c98f0e6c95

Subscribe to this mod's changes

vibe-check is a skill published in the GitHub repository cacheforge-ai/cacheforge-skills (10 stars, last pushed 8mo ago), licensed MIT. It adds 36 tokens to every session and 1,332 once invoked, about $0.0001 per session on Opus 5.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-31.

Code review agent-skills ai-audit code-quality discord discord-v2 javascript linting vibe-coding

Biome

Biome 2.x — fast all-in-one web toolchain in Rust. Formats, lints, assists. Replaces Prettier + ESLint.

pledgeandgrow/pledge-skills · 33 tokens

biome

Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint).

bobmatnyc/claude-mpm-skills · 30 tokens

hone:duplication-hunt

Finds duplicated code patterns across the codebase including exact copies and structural duplication (same logic with different variable names). Ranks by frequency and suggests extraction candidates. Designed for weekly runs. Do NOT use for method length, naming, or style concerns.

ckorhonen/hone-skills · 57 tokens

hone:intent-clarity-audit

Finds code that obscures its intent: unclear variable names, nested ternaries, boolean parameters without names, overly clever one-liners, and comments that restate code instead of explaining why. Focuses on recently changed files. Do NOT use for method length, duplication, or test naming concerns.

ckorhonen/hone-skills · 69 tokens

hone:test-naming-audit

Checks that test method and function names read as complete sentences describing behavior. Flags cryptic names like test1, testFoo, or abbreviated names that do not describe what is being tested. Designed to run on every PR. Do NOT use for test coverage, test structure, or non-test code.

ckorhonen/hone-skills · 66 tokens

hone:method-brevity-audit

Scans a codebase for methods and functions that exceed configurable length thresholds. Reports a ranked list of the longest methods with file:line, language, and surrounding complexity signals. Designed for scheduled weekly runs. Do NOT use for style formatting, indentation, or naming concerns.

ckorhonen/hone-skills · 63 tokens