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/dalvgit/vibecheck/examnpx skills add dalvgit/vibecheck --skill examgit clone --depth 1 https://github.com/dalvgit/vibecheckWhat 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.00067 | $0.00950 |
| Opus 5 | $0.00034 | $0.00475 |
| Sonnet 5 | $0.00013 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
exam 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 2d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibecheck: the exam (Claude Code)
An agent wrote this code; the human is about to put their name on it. Your job is to find out
whether they understand what they're shipping. You are the examiner, not the candidate —
never answer, hint, or narrow the options. AskUserQuestion is the only way to collect an
answer here.
This file is only the Claude Code delivery wrapper. The instructions that decide whether the exam is any good — what to ask, the altitude, fair distractors, how to grade, the one rule — live in the shared guide. Read it before writing questions and follow it:
"$GATE" --guide
0. Find the gate
Every blocked push prints the gate's absolute path on its last line. Use that. If you're run
without a block message (the user just asked to be vibechecked), try
"${CLAUDE_PLUGIN_ROOT}/hooks/gate.sh", and failing that:
ls ~/.claude/plugins/*/vibecheck*/hooks/gate.sh 2>/dev/null || find ~/.claude -name gate.sh -path '*vibecheck*' 2>/dev/null | head -1
1. Read the diff
"$GATE" --diff
This is exactly the diff the gate hashes — do not substitute your own git diff, or the
receipt won't match and the push stays blocked. If it's empty, say so and stop. Use Grep to read
surrounding code (callers, etc.) where a question needs it.
Read .vibecheck.toml if it exists: questions (default 3) and pass (all | majority,
default all).
2. Write the questions
Follow "$GATE" --guide. In short: find the 2–4 ideas the change rests on and test what
follows from them; state the change plainly and make them reason out the consequence; every
distractor actually wrong and distinguishable; never quiz absent code or line-level trivia.
3. Administer via AskUserQuestion
Ask all questions in a single AskUserQuestion call — one per questions entry. The human
answers; you cannot.
Every question carries the way out. Make the last option of every question a plain, first-class escape — same wording each time:
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.
- 2d ago First seen · 85 lines · 67 tokens per session scan A bc80c5f0ada3
exam is a skill published in the GitHub repository dalvgit/vibecheck (4 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 950 once invoked, about $0.0003 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
qc-helper
Answer any question about Qwen Code usage, features, configuration, and troubleshooting by referencing the official user documentation. Also helps users view or modify their settings.json. Invoke with /qc-helper followed by a question, e.g. /qc-helper how do I configure MCP servers? or /qc-helper change approval mode…
agent-newbie-guide
Skill "agent-newbie-guide" from hashgraph-online/awesome-codex-plugins, covering codex 新手引导, 🚫 新手术语过滤（绝对禁止）, 统一行为规范（内嵌）, 📍 阶段位置 and 启动自检.
agent-learning-coach
中文学习教练技能。用于学习编程、英语、设计、产品、AI、数学或任何技能时，先诊断水平，再用讲解、练习、反馈、复习的循环推进。触发语包括"进入学习模式""我想学""带我练""帮我制定学习计划""像教练一样教我"。.
memstack-development-mentor
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.
map-understand
Interactive deep-understanding and quiz mode for MAP sessions. Use when the user wants to understand code, a diff, workflow result, debugging cause, or architecture and be checked with restatements or quizzes.
self-assessment
Interactive skill assessment with personalized learning path generation.