Vibe Coding Mastery

Vibe Coding Mastery is a skill for Claude Code, Codex from LeoYeAI/openclaw-master-skills. It costs 61 tokens per session (6,424 once invoked), scanned A, original, MIT.

A guide to building software with AI coding tools, from writing the first request through deployment, testing, debugging, and deciding whether AI-generated code is suitable for the project.

In plain words
What is it for?
Use it to structure prompts, choose architecture patterns, test and debug generated code, and decide when a prototype is ready for production.
Why use it?
It helps developers choose an appropriate level of AI involvement based on risk, timeline, team size, and data sensitivity. It also explains that reviewing, testing, and understanding generated code is different from accepting it without checking.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Good fit Use it to structure prompts, choose architecture patterns, test and debug generated code, and decide when a prototype is ready for production.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/leoyeai/openclaw-master-skills/afrexai-vibe-coding
About the project

OpenClaw Master Skills is a curated, regularly updated collection of skills that extends an AI personal assistant platform with capabilities such as research, browser automation, presentation creation, and prompt work. It is intended for people using OpenClaw or MyClaw.ai to give their agents additional tasks and workflows. The catalogue contains many skills and agents from this collection.

LeoYeAI/openclaw-master-skills · 2,139 stars · on GitHub · myclaw.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 LeoYeAI/openclaw-master-skills --skill afrexai-vibe-coding
Clone the repo
git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-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.

agentmods badge for Vibe Coding Mastery

README.md
[![agentmods](https://agentmods.dev/badge/skills/leoyeai/openclaw-master-skills/afrexai-vibe-coding/github.svg)](https://agentmods.dev/skills/leoyeai/openclaw-master-skills/afrexai-vibe-coding)
Your own site
<a href="https://agentmods.dev/skills/leoyeai/openclaw-master-skills/afrexai-vibe-coding"><img src="https://agentmods.dev/badge/skills/leoyeai/openclaw-master-skills/afrexai-vibe-coding/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.

agentmods 80×15 button for Vibe Coding Mastery

Your own site · 80×15
<a href="https://agentmods.dev/skills/leoyeai/openclaw-master-skills/afrexai-vibe-coding"><img src="https://agentmods.dev/badge/skills/leoyeai/openclaw-master-skills/afrexai-vibe-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,424 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 112
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 587
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 489
    Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.
    Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.06424
Opus 5 $0.00030 $0.03212
Sonnet 5 $0.00012 $0.01285
Haiku 4.5 $0.00006 $0.00642

Measured 7d ago against content hash a6fcc8d8e392, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

Vibe Coding Mastery 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.

skills/afrexai-vibe-coding/SKILL.md · 667 lines

How it starts

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

Vibe Coding Mastery

The complete system for building software with AI — from zero to production. Not tips. Not theory. A full operating methodology.

What is vibe coding? Programming where you describe what you want and let AI generate code. You evaluate by results, not by reading every line. Coined by Andrej Karpathy (Feb 2025).

Key distinction (Simon Willison): If you review, test, and explain the code — that's AI-assisted software development. Vibe coding means accepting AI output without fully understanding every function. This skill covers both modes and the spectrum between them.


Phase 1: When to Vibe (Decision Matrix)

Before starting, classify your project:

Factor Vibe ✅ Don't Vibe ❌
Stakes Low (prototype, internal, learning) High (payments, auth, compliance)
Timeline Hours to days Months+
Team size Solo or pair Large team with standards
Domain knowledge You understand the domain Unfamiliar territory
Reversibility Easy to rewrite Hard to change later
Data sensitivity Public/test data PII, financial, health

Scoring: Count ✅ checks.

  • 5-6: Full vibe mode. Ship fast.
  • 3-4: Vibe with guardrails. Review critical paths.
  • 1-2: AI-assisted development, not vibe coding. Review everything.
  • 0: Write it yourself or hire someone who understands the domain.

Vibe Coding Maturity Levels

Level Description Who
L1 — Passenger Copy-paste AI output, hope it works Beginners
L2 — Navigator Guide AI with context, catch obvious errors Intermediate
L3 — Pilot Architecture decisions, AI implements, you review Experienced devs
L4 — Conductor Orchestrate multiple AI sessions, parallel streams Power users

Target: L3 minimum for anything going to production.


Phase 2: Tool Selection

Primary Tools Matrix

Tool Best For Context Window Multi-file Terminal Cost
Claude Code Full-stack, complex refactors, CLI 200K Excellent Native API usage
Cursor Editor-integrated, rapid iteration 128K Good Via terminal $20/mo + API
Windsurf Beginner-friendly, guided flows 128K Good Limited $10/mo + API
GitHub Copilot Inline completions, small edits 8-32K Limited No $10-19/mo
Aider Git-aware, open source, CLI Varies Good Native API only
Cline (VS Code) VS Code native, plan mode Varies Good Via terminal API only

Read the full file on GitHub · 667 lines

Files

What ships with it

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

  1. 7d ago First seen · 667 lines · 61 tokens per session scan A a6fcc8d8e392

Subscribe to this mod's changes

Vibe Coding Mastery is a skill published in the GitHub repository LeoYeAI/openclaw-master-skills (2,139 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 6,424 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-09-03.

Related

Other skills, from other repositories

contract

Outcome-driven Cortex function development — declares a behavioral contract before generation begins, enforces evidence-tiered proof before $ship, and defends against the self-oracle evaluation failure mode.

Snowflake-Labs/cocoplus · 38 tokens

spec-driven-development

Design and run a Spec-Driven Development (SDD) pipeline for AI software factories — where structured specifications are the input, AI agents generate the code, and quality gates enforce correctness at each phase: SPECIFY → DECOMPOSE → IMPLEMENT → VERIFY → DELIVER. Use when building or refining a spec-driven pipeline…

magnus919/agent-skills · 165 tokens

red-green-refactor

Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…

rohitg00/skillkit · 90 tokens

drill-tdd

Use when implementing any feature or bugfix — enforces the Red-Green-Refactor drill with no production code allowed without a failing test first.

kucherenko/gangsta · 34 tokens

the-hit

Use when the execution plan is approved and it is time for parallel execution — dispatches workers through crew leads to implement work packages with TDD enforcement, report collection, and escalation protocols.

kucherenko/gangsta · 39 tokens

gherkin-and-dsl

Evaluate and refactor Gherkin feature files and DSL vocabularies so they can be implemented as test code with minimal inference. Use when converting test plans into Gherkin, reviewing or tightening Given/When/Then sentences, deciding Rule/Background/Scenario Outline/DataTable structure, or checking whether Gherkin and…

YuDefine/nuxt-supabase-starter · 78 tokens