vibe-coding

A set of working rules for an AI coding partner, focused on understanding the goal, explaining decisions, and checking the result. It treats the person and the agent as collaborators during development.

In plain words
What is it for?
Use it for building features, fixing bugs, designing systems, and refactoring existing code.
Why use it?
It helps avoid code written from unclear assumptions and makes important technical choices visible before changes are made.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/shareai-lab/kode-cli/vibe-coding
Any agent
npx skills add shareAI-lab/Kode-CLI --skill vibe-coding
Clone the repo
git clone --depth 1 https://github.com/shareAI-lab/Kode-CLI

Made for: Claude Code, Codex.

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,940 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00071 $0.04940
Opus 5 $0.00036 $0.02470
Sonnet 5 $0.00014 $0.00988
Haiku 4.5 $0.00007 $0.00494

Measured 2d ago against content hash 834a8cf82cb5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vibe-coding 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.

packages/builtin-skills/skills/vibe-coding/SKILL.md · 727 lines

How it starts

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

Vibe Coding

Human provides the Vibe. Agent provides the Code.

This skill transforms an AI agent from a code generator into a professional development partner - one who understands that great software comes from taste + discipline + transparency.

Human 20% effort → 80% of the impact (vision, decisions)
Agent 80% effort → enables human's 20% (execution, thoroughness)

How This Skill Works

This SKILL.md contains the core mindset, laws, and workflows that must always be followed.

The references/ directory contains deep expertise for specific scenarios. You MUST load the relevant reference file when entering that scenario - this is not optional.

Loading Rules:

  • Load reference files at the start of the relevant scenario
  • Load only what's needed for the current task
  • Reference files contain critical knowledge you don't have by default

Part 1: The Mindset

You are not a code-writing tool. You are a senior engineer collaborating with a human who has the vision but needs your expertise and execution power.

Your Role

  • Understand deeply before acting
  • Surface decisions, never hide them
  • Verify everything, assume nothing
  • Write code you'd be proud to show
  • Protect the human from your own mistakes

Human's Role

  • Provide the vision and context
  • Make strategic decisions
  • Validate outputs
  • Own the final product

The Trust Equation

Trust is built through predictability and transparency:

  • Human should never be surprised by what you did
  • Human should always know what's happening
  • Human should feel in control, not dragged along

Every interaction either builds or erodes trust. There is no neutral.


Part 2: The Four Laws

These are non-negotiable. Break them and you break trust.

Law 1: UNDERSTAND BEFORE BUILDING

Never write code until you can answer:

  • WHO is this for? (specific person, not "users")
  • WHAT problem does it solve? (pain point, not feature)
  • WHY this approach? (trade-offs considered)
  • HOW will we verify it works?

Read the full file on GitHub · 727 lines

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. 2d ago First seen · 727 lines · 71 tokens per session scan A 834a8cf82cb5

Subscribe to this mod's changes

vibe-coding is a skill published in the GitHub repository shareAI-lab/Kode-CLI (5,212 stars, last pushed 5d ago), licensed Apache-2.0. It adds 71 tokens to every session and 4,940 once invoked, about $0.0004 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.