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.
git clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kitnpx agentmods add skills/giang6283623/minimal-vibe-coding-kit/vibekit-initWrote 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/giang6283623/minimal-vibe-coding-kit/vibekit-init)<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/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/giang6283623/minimal-vibe-coding-kit/vibekit-init"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/vibekit-init.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.00070 | $0.00910 |
| Opus 5.5 | $0.00028 | $0.00364 |
| Sonnet 5.5 | $0.00014 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
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 17d 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 multiple-choice questions` procedure in `.vibekit/init/FIRST_TIME_INIT.md`. Ask it only when Codex is installed and supports it. Recommend Yes with its short reason, treat No as temporary, How it starts
The opening of the file, as written. The whole thing — 60 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
- Print the requirements checklist from
.vibekit/init/FIRST_TIME_INIT.md. - Run or emulate detection, including repo-specific conventions, project mode, and PRD presence:
node .vibekit/scripts/init-backbone.mjs . --propose
- Run the project-understanding step below.
- Run the Codex setup preference below when Codex is installed and supports it.
- Propose a unified diff for
backbone.yml, itsconventionsrules, managed blocks, any new.vibekit/docs/PRD.md, and approved Codex preference files. - Ask:
Apply this proposed backbone and convention rules? Reply yes, edit, or abort. - Write only after explicit
yes. - Validate after writing.
Ask every first-init question in the plain style from Question style (first init) in .vibekit/init/FIRST_TIME_INIT.md: coding level 0 words, ASD-STE100 in English, one topic, 2 or 3 numbered choices, no config keys.
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.mdfrom.vibekit/docs/templates/PRD_TEMPLATE.mdusing the answers, and setproject.prdto 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 inproject.context.
Codex setup preference
Follow the three-choice Codex multiple-choice questions procedure in .vibekit/init/FIRST_TIME_INIT.md. Ask it only when Codex is installed and supports it. Recommend Yes with its short reason, 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.
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.
- 17d ago Changed · +2 lines defb28e73e30
- 2mo ago First seen · 58 lines · 70 tokens per session scan B 214d61920cfb
vibekit-init is a skill published in the GitHub repository giang6283623/minimal-vibe-coding-kit (26 stars, last pushed 18d ago), licensed MIT. It adds 70 tokens to every session and 910 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.