Agent skill

Vibe Agents Instructions

by KhazP in KhazP/vibe-coding-prompt-template

Writes project agent instructions and tool setup from decided requirements and the existing repo, keeping only stable, non-obvious guidance in always-loaded files.

MITAuto-check: notesAgent Workflows

Install Vibe Agents Instructions

skills CLI
$ npx skills add KhazP/vibe-coding-prompt-template --skill vibe-agents -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install KhazP/vibe-coding-prompt-template vibe-agents --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vibe-agents .claude/skills/vibe-agents && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-agents
GitHub stars
3.1k
Token cost
~421 tokens
SKILL.md length
203 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Writes project agent instructions and tool setup from decided requirements and the existing repo, keeping only stable, non-obvious guidance in always-loaded files.

  • Creating an AGENTS.md for a new project once the PRD and tech design are settled
  • Calls npx
  • Updating a few agent instructions after a technical decision changes
  • Setting up Vibe Workflow files in a repository with the vibeworkflow CLI

What it does

The agent works from agreed requirements, technical decisions and the existing repository, and writes only guidance that is stable and not obvious from the code. For a small change it edits the affected AGENTS.md instructions directly, with no installer, fresh PRD or full interview, and progress tracking belongs in the project's memory or handoff file, not in the rules that load every session.

For first-time Vibe Workflow setup it uses the configured manifest paths and, when the vibeworkflow CLI is available, inspects the output of `npx vibeworkflow --dry-run --json` before initializing within what you have authorized. Existing files are preserved unless a reviewed replacement is intended. Task-specific procedures go into skills or references that load on demand, broad tool permissions are not switched on for convenience, and `npx vibeworkflow doctor` checks configuration only, not a working build. In a chat without filesystem access it produces separate files to save, based on docs/context-pack.md and the product decisions supplied.

When your agent uses it

  • Creating an AGENTS.md for a new project once the PRD and tech design are settled
  • Updating a few agent instructions after a technical decision changes
  • Setting up Vibe Workflow files in a repository with the vibeworkflow CLI
  • Producing instruction files from a chat that has no filesystem access

Example prompts

  • “Create AGENTS.md for this repo based on the PRD and tech design we agreed on.”
  • “Update the testing section of AGENTS.md now that we moved from Jest to Vitest.”
  • “Run a dry run of vibeworkflow and list the files it would add before you initialize anything.”

Requirements

  • Node.js with npx, when using the vibeworkflow CLI
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

What it can do on your machine

Read from SKILL.md and the folder at commit d26fb0d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • Bash
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Agents Instructions loads about 421 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 203 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~421

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from KhazP/vibe-coding-prompt-template at commit d26fb0d, republished under its MIT licence (© KhazP). 203 words, ~421 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-agents/SKILL.md (or your agent's skills folder).
name
vibe-agents
description
Create project agent instructions and tool configuration from agreed product and technical decisions.
allowed-tools
Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

Project agent instructions

Use agreed requirements, technical decisions, and the existing repository to write only stable, non-obvious guidance. For a targeted AGENTS.md edit, update the affected instructions directly; do not require an installer, new PRD, or full interview. Keep progress in the project's memory/handoff file rather than the always-loaded rules.

For initial Vibe Workflow setup, use the configured manifest paths. If the vibeworkflow CLI is available, inspect npx vibeworkflow --dry-run --json and initialize within the user's authorization. Preserve existing files; replacement flags are for intentional replacements whose affected files have been reviewed. The CLI installs files directly, not into a new templates/ directory.

Fill relevant placeholders from known decisions. Keep task-specific procedures in skills or references and load them only when relevant. Distinguish local implementation from external sends, production changes, and new access. Do not enable broad tool permissions just to make setup convenient.

Use npx vibeworkflow doctor for CLI-generated setup when available; it checks configuration, not a working build or user journey. In a chat without filesystem access, use the repository's docs/context-pack.md and supplied product decisions to produce separated files to save. State absent template/context limitations instead of inventing them. Continue into implementation only when that is part of the user's request.

© KhazP, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/vibe-agents of KhazP/vibe-coding-prompt-template.

Open the folder on GitHubat commit d26fb0d

Compare with similar skills

Vibe Agents Instructions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Agents Instructions compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Agents Instructions this skillKhazP/vibe-coding-prompt-template3.1k—~421Automated safety check: NotesMIT
Intent Layercrafter-station/skills1121 repos~633Automated safety check: PassMIT
AI Bomcdxgen/cdxgen1.1k—~2.5kAutomated safety check: PassApache-2.0
AI Context Workspace Initkvker/ai-context-workspace101—~948Automated safety check: PassMIT
Add Remote Endpointnextcloud/android-library106—~1.1kAutomated safety check: PassCustom licence
AGENTS.md Scaffoldmajiayu000/spellbook287—~1.5kAutomated safety check: PassMIT

Similar skills

  • Intent Layer

    crafter-station/skills

    Set up hierarchical Intent Layer (AGENTS.md files) for codebases.

    112 GitHub starsUsed in 1 repo~633 tokens
    Agent WorkflowsAuto-check passed
  • AI Bom

    cdxgen/cdxgen

    Generates AI-BOM, MCP inventory, AI skill inventory, and AI authorship provenance documents with cdxgen, cataloging models, inference services, Hugging Face purls, MCP servers and their…

    1.1k GitHub stars~2.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • AI Context Workspace Init

    kvker/ai-context-workspace

    Turns existing work units or an empty directory into an AI Context Workspace by scanning materials, generating background and conventions, and installing runtime skills.

    101 GitHub stars~948 tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Add Remote Endpoint

    nextcloud/android-library

    A skill your agent uses when adding a new remote/network endpoint (a RemoteOperation / OCSRemoteOperation) to this Nextcloud Android library, or when the user says "add an endpoint", "new remote…

    106 GitHub stars~1.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • AGENTS.md Scaffold

    majiayu000/spellbook

    Scans a repository for real evidence and proposes, or on request writes, a small stack of root and scoped AGENTS.md files with validation commands and generated-file boundaries.

    287 GitHub stars~1.5k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Scaffold Claude

    ragnar-pwninskjold/tech-snacks

    A skill your agent uses when the user wants to create, draft, or scaffold a CLAUDE.md (or AGENTS.md) file for their project.

    137 GitHub stars~1.7k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

More from KhazP/vibe-coding-prompt-template

All 11 skills in this repo
  • MVP Product Requirements Writer

    KhazP/vibe-coding-prompt-template

    Writes or revises an MVP product requirements document, sized to the product, with observable acceptance criteria and no repeated questions.

    3.1k GitHub stars~455 tokensUpdated 5 days ago
    Auto-check passed
  • Vibe Research

    KhazP/vibe-coding-prompt-template

    Researches an app idea or settles product and technical uncertainties before a design is fixed, and saves the findings with a handoff for the next stage.

    3.1k GitHub stars~473 tokensUpdated 5 days ago
    Auto-check passed
  • MVP Technical Design

    KhazP/vibe-coding-prompt-template

    Writes an MVP technical design from agreed requirements, covering architecture, data ownership, integration contracts, deployment and tradeoffs, then hands off to the next stage.

    3.1k GitHub stars~512 tokensUpdated 5 days ago
    Auto-check passed
  • Vibe Debug

    KhazP/vibe-coding-prompt-template

    A short debugging procedure for an existing project: reproduce the failure, test one hypothesis at a time, make the smallest fix, add a regression check and re-verify.

    3.1k GitHub stars~403 tokensUpdated 5 days ago
    Auto-check: notes
  • Vibe Workflow Router

    KhazP/vibe-coding-prompt-template

    Picks the next useful step for an app project, whether planning a new product, changing an existing app, fixing a bug or writing a handoff, loading only the context needed.

    3.1k GitHub stars~544 tokensUpdated 5 days ago
    Auto-check: notes
  • Build a New-Project Slice

    KhazP/vibe-coding-prompt-template

    Builds one working slice of a new project from the brief, runs the affected checks and the user journey, and reports what was and was not verified.

    3.1k GitHub stars~353 tokensUpdated 5 days ago
    Auto-check: notes

Categories

Questions about Vibe Agents Instructions

What does Vibe Agents Instructions do?

Writes project agent instructions and tool setup from decided requirements and the existing repo, keeping only stable, non-obvious guidance in always-loaded files. The agent works from agreed requirements, technical decisions and the existing repository, and writes only guidance that is stable and not obvious from the code.md instructions directly, with no installer, fresh PRD or full interview, and progress tracking belongs in the project's memory or handoff file, not in the rules that load every session.

When should I use Vibe Agents Instructions?

Vibe Agents Instructions fits situations like: creating an AGENTS.md for a new project once the PRD and tech design are settled; updating a few agent instructions after a technical decision changes; setting up Vibe Workflow files in a repository with the vibeworkflow CLI; producing instruction files from a chat that has no filesystem access.

How do I install Vibe Agents Instructions in Claude Code?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-agents -a claude-code`. Or copy the skill folder (.agents/skills/vibe-agents in KhazP/vibe-coding-prompt-template) into .claude/skills/vibe-agents in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Agents Instructions in Codex?

Run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-agents -a codex`. Or copy the skill folder (.agents/skills/vibe-agents in KhazP/vibe-coding-prompt-template) into .agents/skills/vibe-agents in your project. Codex loads it when a task matches its description.

Can I use Vibe Agents Instructions in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KhazP/vibe-coding-prompt-template --skill vibe-agents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-agents, .gemini/skills/vibe-agents, .github/skills/vibe-agents and .opencode/skills/vibe-agents in your project.

What does Vibe Agents Instructions need to run?

Going by SKILL.md and its folder, Vibe Agents Instructions needs the command-line tools its instructions call (npx). Our summary lists: Node.js with npx, when using the vibeworkflow CLI. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion.

Does Vibe Agents Instructions access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Vibe Agents Instructions safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Vibe Agents Instructions use?

Vibe Agents Instructions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Agents Instructions use?

About 421 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vibe Agents Instructions?

Skills that share tags, products or a category with Vibe Agents Instructions: Intent Layer (crafter-station/skills, 112 stars), AI Bom (cdxgen/cdxgen, 1.1k stars), AI Context Workspace Init (kvker/ai-context-workspace, 101 stars) and Add Remote Endpoint (nextcloud/android-library, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Agents Instructions?

KhazP (a GitHub user) maintains it in KhazP/vibe-coding-prompt-template, which has 3,130 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 4, 2026.

Source: KhazP/vibe-coding-prompt-template on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.