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 agentmods add instructions/giang6283623/minimal-vibe-coding-kit/claude-mdgit clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kitWrote 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/instructions/giang6283623/minimal-vibe-coding-kit/claude-md)<a href="https://agentmods.dev/instructions/giang6283623/minimal-vibe-coding-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/giang6283623/minimal-vibe-coding-kit/claude-md.svg" alt="Measured on agentmods" 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.00678 | $0.00678 |
| Opus 5 | $0.00339 | $0.00339 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
minimal-vibe-coding-kit CLAUDE.md 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
Claude Code
This file is intentionally small. Shared rules live in AGENTS.md, project facts live in backbone.yml, and long procedures live in .claude/skills/.
Startup
- Read
backbone.yml. - If
meta.template_statusisuninitialized, follow.vibekit/init/FIRST_TIME_INIT.mdbefore other work. - If initialized, follow
backbone.ymlconventionsand continue with the user's task.
Useful skills
/init-vibe- initialize or repair the kit setup./autoresearch-coding- run a metric-driven improvement loop./security-scan- run AgentShield-style review./daily-enhance- propose rule, skill, and workflow improvements./coding-level N- set explanation depth 0-5; the project default lives inbackbone.ymlconventions.custom_rules./prompt-sharpener <rough prompt>- sharpen a rough prompt into a precise one, then execute it in the same turn./claim <request>- vet a request to bring something new into the repo (validate sources, fit-check, confirm, integrate, document)./wait-what [the part that lost you]- the last message did not land; stop and re-pitch it in plain language, in the user's language, with the project glossary./tutien- private, funny xianxia "cultivation" progress report from Git history + supplied AI-chat exports;/tutien offdisables it./the-creator level N- create a novel but workable result while cumulatively relaxing 10% of eligible conventions per level.
Hard rules
- Show a diff and wait for explicit approval before changing root instruction files,
backbone.yml, rules, skills, or workflows. - Do not deploy, rotate secrets, run migrations, delete data, or rewrite remote history without explicit approval.
- Prefer
trashoverrmfor deletions; permanent deletes need explicit approval of the exact paths (see.claude/rules/safe-delete.md). - Keep
.autoresearch/,results.tsv, and.vibekit/reports/local unless the user asks to commit them.
English Learning & Grammar Correction
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.
- 5d ago First seen · 60 lines · 678 tokens per session scan A a30003cdc623
minimal-vibe-coding-kit CLAUDE.md is an instructions file published in the GitHub repository giang6283623/minimal-vibe-coding-kit (21 stars, last pushed 8d ago), licensed MIT. It adds 678 tokens to every session, about $0.0034 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).