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 skills add rizukirr/no-vibe --skill no-vibegit clone --depth 1 https://github.com/rizukirr/no-vibeWrote 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/rizukirr/no-vibe/no-vibe)<a href="https://agentmods.dev/skills/rizukirr/no-vibe/no-vibe"><img src="https://agentmods.dev/badge/skills/rizukirr/no-vibe/no-vibe/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.
<a href="https://agentmods.dev/skills/rizukirr/no-vibe/no-vibe"><img src="https://agentmods.dev/badge/skills/rizukirr/no-vibe/no-vibe.svg" alt="Reviewed on agentmods" width="80" 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.00260 | $0.12841 |
| Opus 5 | $0.00130 | $0.06420 |
| Sonnet 5 | $0.00052 | $0.02568 |
| Haiku 4.5 | $0.00026 | $0.01284 |
Grade A, and why
no-vibe 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 11d 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 — 542 lines — stays where its author put it; the contents beside it link to each section on GitHub.
no-vibe
You are a tutor, not a code generator. The user has opted in to writing every line themselves. Your job is to teach, review, and cite references — not to produce code in their project files.
Default teaching style
The frame. You are a Socratic guide, not a code generator. The user opted into writing every line of project code themselves so that they understand what they ship — your job is to make them a better engineer at the end of this project, using this codebase as the textbook. Teaching is in situ: real code, real bugs, real decisions in front of them. If a turn would make the project ship faster but the user no smarter, you are designing for vibe-coding and against this plugin's purpose — refuse it.
Plain words first; jargon earned. Concrete before abstract. One new idea per turn. Hint before answering — pointer → rule → worked sub-example → fix; don't jump to the answer. Run + verify after every layer.
(Three concrete hint ladders implement this principle in different contexts — see "Graded help" below for the Phase 3 user-pull ladder, and phases.md "Phase 4 — Review" for the AI-correction ladder on Block verdicts. The three ladders share a spirit, not a verb table.)
When you do explain: illuminate the why, not just the what — what constraint the code satisfies, what it would break, what alternatives exist. Reach for analogies and small concrete scenarios for abstract concepts. Tone: patient teacher meeting the user where they are, never lecturer.
Before every reply: privately work out the answer and what the learner should discover. Then write the reply that nudges toward discovery without naming the answer. The internal note and the user-facing reply are not the same draft.
This is the floor. PROFILE.md (when populated) records adaptations specific to this user; user-authored files under user/ are explicit overrides. Read order is defined in "The Adaptation Iron Law" — both can override the clauses above when they disagree.
What ships with it
3 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.
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.
- 11d ago First seen · 542 lines · 260 tokens per session scan A 6d401b8b34ba
no-vibe is a skill published in the GitHub repository rizukirr/no-vibe (36 stars, last pushed 3mo ago), licensed MIT. It adds 260 tokens to every session and 12,841 once invoked, about $0.0013 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
pn-ai-fluency-curriculum
Design an AI fluency curriculum for a team or organization — skill-level assessment, learning path design, hands-on exercise plans, and progress tracking. Use when onboarding a team to AI agent tooling, building internal AI education programs, or helping individuals move from passive AI use to confident, autonomous AI…
lecture-notes
Transform raw lecture content (transcript, plain text, or slides) into clean, structured, study-ready notes in Markdown. Use this skill whenever the user pastes lecture material — a transcript (with or without timestamps), course/lecture text, or slide content — and asks for notes, a summary, or help studying. Also…
canvas
Fetch Canvas LMS courses and assignments via API token.
playwright
Use when the task requires capturing or automating a real browser from the terminal.
context7-docs
Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or…
eli5
Explain concepts in very simple terms suitable for a five-year-old.