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.
npx agentmods add skills/cacheforge-ai/cacheforge-skills/vibe-checknpx skills add cacheforge-ai/cacheforge-skills --skill vibe-checkgit clone --depth 1 https://github.com/cacheforge-ai/cacheforge-skillsWrote 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/cacheforge-ai/cacheforge-skills/vibe-check)<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="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 | $0.00036 | $0.01332 |
| Opus 5 | $0.00018 | $0.00666 |
| Sonnet 5 | $0.00007 | $0.00266 |
| Haiku 4.5 | $0.00004 | $0.00133 |
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 4d 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 — 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 FindingsShow Fix SuggestionsRun 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 |
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.
- CHANGELOG.md 2.3 KB
- LICENSE 1.0 KB
- README.md 9.5 KB
- scripts/analyze.sh 15 KB runs code
- scripts/common.sh 6.3 KB runs code
- scripts/git-diff.sh 2.3 KB runs code
- scripts/report.sh 12 KB runs code
- scripts/vibe-check.sh 7.7 KB runs code
- SECURITY.md 2.2 KB
- test_samples/bad_api.py 2.2 KB runs code
- test_samples/decent_utils.py 3.3 KB runs code
- TESTING.md 2.5 KB
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.
- 4d ago First seen · 155 lines · 36 tokens per session scan A 41c98f0e6c95
vibe-check is a skill published in the GitHub repository cacheforge-ai/cacheforge-skills (10 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,332 once invoked, about $0.0002 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-31.
Other skills, from other repositories
Biome
Biome 2.x — fast all-in-one web toolchain in Rust. Formats, lints, assists. Replaces Prettier + ESLint.
eslint-docs
ESLint 10.x — flat config, rules, plugins, formatters, parsers, CLI, Node.js API, custom rules, migration.
biome
Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint).
biome
Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint).
implement
Research, implement, test, document, and review a Fallow feature, fix, refactor, or repository improvement. Use when asked to build or change Fallow.
open-draft-pr
Prepare local changes for review with an intentional commit, push, and ready PR for fallow. Use when the user wants to publish work, open a PR, or turn local changes into a reviewable branch.