vibekit-init

vibekit-init is a skill for Claude Code, Codex from giang6283623/minimal-vibe-coding-kit. It costs 70 tokens per session (842 once invoked), scanned B, original, MIT.

A workflow for setting up or repairing the Minimal Vibe Coding Kit in an existing project. It examines the project, proposes changes to shared instructions and documentation, and waits for approval before writing anything.

In plain words
What is it for?
Use it to initialize backbone.yml, merge project guidance files, set up tool-specific rules, create a product requirements document, and validate the resulting setup.
Why use it?
It helps combine project rules across tools while showing the proposed changes first. This reduces accidental overwrites of existing instructions or project decisions.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also reads ~/.codex or $CODEX_HOME. Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents); mentions AGENTS.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node .vibekit/scripts/init-backbone.mjs . --propose.

Good fit Use it to initialize backbone.yml, merge project guidance files, set up tool-specific rules, create a product requirements document, and validate the resulting setup.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kit
agentmods
npx agentmods add skills/giang6283623/minimal-vibe-coding-kit/vibekit-init

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 vibekit-init

README.md
[![agentmods](https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/vibekit-init.svg)](https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/vibekit-init)
Your own site
<a href="https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/vibekit-init"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/vibekit-init.svg" alt="Measured on agentmods" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 842 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00070 $0.00842
Opus 5 $0.00035 $0.00421
Sonnet 5 $0.00014 $0.00168
Haiku 4.5 $0.00007 $0.00084

Measured 8d ago against content hash 214d61920cfb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

vibekit-init scanned grade B with 1 finding 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 8d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Follow the three-choice `Codex structured questions in Default mode` procedure in `.vibekit/init/FIRST_TIME_INIT.md`. Recommend Yes with its short benefit, treat No as temporary, persist Don't show this again as project-
.agents/skills/vibekit-init/SKILL.md · 58 lines

How it starts

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

Vibe Kit Init

Initialize the kit safely.

Required behavior

  1. Print the requirements checklist from .vibekit/init/FIRST_TIME_INIT.md.
  2. Run or emulate detection, including repo-specific conventions, project mode, and PRD presence:
node .vibekit/scripts/init-backbone.mjs . --propose
  1. Run the project-understanding step below.
  2. Run the Codex setup preference below when Codex is installed and supports it.
  3. Propose a unified diff for backbone.yml, its conventions rules, managed blocks, any new .vibekit/docs/PRD.md, and approved Codex preference files.
  4. Ask: Apply this proposed backbone and convention rules? Reply yes, edit, or abort.
  5. Write only after explicit yes.
  6. Validate after writing.

Project understanding (PRD)

Detection reports project.mode (greenfield = no source yet, brownfield = existing code) and whether a PRD exists.

  • Always offer a short interview, regardless of whether docs already exist: what the project is and who it is for, the core problem and primary focus now, what success looks like, key constraints/non-goals, and (brownfield) which area to improve first.
  • If no PRD is found, propose creating .vibekit/docs/PRD.md from .vibekit/docs/templates/PRD_TEMPLATE.md using the answers, and set project.prd to that path.
  • If a PRD exists, read it, link it in project.prd, and offer to refresh it without overwriting unapproved content.
  • Keep the PRD short; it captures intent, not a full spec. Record domain terms in .vibekit/docs/CONTEXT.md (scaffold from .vibekit/docs/templates/CONTEXT_TEMPLATE.md) and link it in project.context.

Codex setup preference

Follow the three-choice Codex structured questions in Default mode procedure in .vibekit/init/FIRST_TIME_INIT.md. Recommend Yes with its short benefit, treat No as temporary, persist Don't show this again as project-local dismissal, and never edit the user's global ~/.codex/config.toml. Include any resulting .codex/config.toml or .vibekit/preferences.json change in the approval diff.

Read the full file on GitHub · 58 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. 8d ago First seen · 58 lines · 70 tokens per session scan B 214d61920cfb

Subscribe to this mod's changes

vibekit-init is a skill published in the GitHub repository giang6283623/minimal-vibe-coding-kit (21 stars, last pushed 10d ago), licensed MIT. It adds 70 tokens to every session and 842 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens