vibe-agents

vibe-agents is a skill for Claude Code, Codex from KhazP/vibe-coding-prompt-template. It costs 52 tokens per session (2,741 once invoked), scanned A, original, MIT.

A guided tool for creating AGENTS.md and other configuration files that tell AI coding assistants how to work on a project.

In plain words
What is it for?
It helps set up an AI-assisted project, record the main plan in AGENTS.md, store supporting details in agent_docs, and create tool-specific agent configuration.
Why use it?
It turns project decisions and working rules into files an assistant can follow, while asking questions when important details are missing.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Good fit It helps set up an AI-assisted project, record the main plan in AGENTS.md, store supporting details in agent_docs, and create tool-specific agent configuration.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/khazp/vibe-coding-prompt-template/vibe-agents
About the project

KhazP/vibe-coding-prompt-template is a collection of templates and workflows that use large language models to turn an idea into a product requirements document, technical design, and minimum viable product plan. It is for people building MVPs with AI coding agents or chat tools, and its catalogue entries support that planning and coding workflow.

KhazP/vibe-coding-prompt-template · 3,050 stars · on GitHub · vibeworkflow.app

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.

Any agent
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-agents
Clone the repo
git clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-template

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 vibe-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/khazp/vibe-coding-prompt-template/vibe-agents/github.svg)](https://agentmods.dev/skills/khazp/vibe-coding-prompt-template/vibe-agents)
Your own site
<a href="https://agentmods.dev/skills/khazp/vibe-coding-prompt-template/vibe-agents"><img src="https://agentmods.dev/badge/skills/khazp/vibe-coding-prompt-template/vibe-agents/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.

agentmods 80×15 button for vibe-agents

Your own site · 80×15
<a href="https://agentmods.dev/skills/khazp/vibe-coding-prompt-template/vibe-agents"><img src="https://agentmods.dev/badge/skills/khazp/vibe-coding-prompt-template/vibe-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,741 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 175
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Memory Poisoning · line 94
    Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.
    Fix: Do not allow untrusted input to persist in agent memory or context. Validate all content before storing and implement memory isolation between sessions.
  • medium Excessive Agency · line 180
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.00052 $0.02741
Opus 5 $0.00026 $0.01371
Sonnet 5 $0.00010 $0.00548
Haiku 4.5 $0.00005 $0.00274

Measured 9d ago against content hash 37510c63568c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

vibe-agents 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 9d 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.

.agents/skills/vibe-agents/SKILL.md · 309 lines

How it starts

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

Vibe-Coding Agent Configuration Generator

You are helping the user create AGENTS.md and tool-specific configuration files. This is Step 4 of the vibe-coding workflow.

Your Role

Generate the instruction files that guide AI coding assistants to build the MVP. Use progressive disclosure - master plan in AGENTS.md, details in agent_docs/.

Interview Rules

  • Use your native question tool (e.g. AskUserQuestion in Claude Code) to ask questions when available; otherwise ask in plain chat.
  • Ask one question at a time by default: ask, wait for the answer, then continue.
  • If the user answers several questions at once, accept those answers, skip the questions they covered, and carry on with the ones still open. Never re-ask something they already told you.
  • If the user says "I don't know" or seems unsure, propose a sensible default and ask them to confirm it rather than leaving the answer blank.
  • Never invent an answer they did not give. If a reply is vague, ask one short follow-up.
  • Cover every question in the lists below — but let the user's own answers, and anything a ## Handoff Context block already supplies, close them out.

Session Continuity

  1. Keep Step 4 outputs aligned with prior PRD and Tech Design context.
  2. If prior chat context is missing, require a compact handoff summary before generating files.
  3. Add continuity hints in generated instructions so users avoid empty-chat resets during Step 5.

Naming Policy

Use model family names in examples and recommendations unless the user explicitly requests pinned versions.

Prerequisites

  1. Look for docs/PRD-*.md - REQUIRED
  2. Look for docs/TechDesign-*.md - REQUIRED
  3. If either is missing, suggest running the appropriate skill first

Step 1: Load Context

Extract from documents:

From PRD:

  • Product name and description
  • Primary user story
  • All must-have features
  • Nice-to-have and excluded features
  • Success metrics
  • UI/UX requirements
  • Timeline and constraints

From Tech Design:

  • Complete tech stack
  • Project structure
  • Database schema
  • Implementation approach
  • Deployment platform
  • AI tool recommendations
  • AI provider strategy, product AI decisions, verification commands, and data/privacy constraints

Read the full file on GitHub · 309 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. 9d ago First seen · 309 lines · 52 tokens per session scan A 37510c63568c

Subscribe to this mod's changes

vibe-agents is a skill published in the GitHub repository KhazP/vibe-coding-prompt-template (3,050 stars, last pushed 3d ago), licensed MIT. It adds 52 tokens to every session and 2,741 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

vibe-coding-guardian

Behavioral modifier for AI coding assistants working with non-developers. Adapts AI behavior by risk level — fast for small changes, cautious for risky ones. Prevents debug death spirals, translates errors to plain language, auto-checkpoints with git, and runs periodic health checks. Always active, zero manual trigger…

kanyun-inc/reskill · 73 tokens

moai-workflow-thinking

Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.

modu-ai/moai-adk · 43 tokens

code-mate-antigravity

Runs Antigravity CLI headlessly for repository analysis and coding tasks. Use when the user asks to delegate work to Antigravity CLI or compare its result with another coding agent.

CherryHQ/cherry-studio · 43 tokens

code-mate-openclaw

Runs a local OpenClaw agent non-interactively and returns its structured response. Use when the user asks to delegate a bounded task to the OpenClaw main agent.

CherryHQ/cherry-studio · 41 tokens

code-mate-qoder

Runs the Code Mate Qoder CN CLI non-interactively with structured output. Use when the user asks to delegate a bounded coding task to Qoder.

CherryHQ/cherry-studio · 36 tokens

office-hours

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…

GCWing/BitFun · 168 tokens