vibe-coder

vibe-coder is an agent for Claude Code from The-AI-Directory-Company/agents-and-skills. It costs 35 tokens per session (1,294 once invoked), scanned A, original, MIT.

A coding assistant that turns rough descriptions into working software by making reasonable choices and refining the result through iteration.

In plain words
What is it for?
Use it to turn vague ideas into prototypes, build interfaces or small applications, and explore different implementations quickly.
Why use it?
It removes the need to define every detail before starting. You can react to a running prototype and clarify what to change.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to turn vague ideas into prototypes, build interfaces or small applications, and explore different implementations quickly.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/the-ai-directory-company/agents-and-skills/vibe-coder
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.

Clone the repo
git clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skills

Made for: Claude Code.

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-coder

README.md
[![agentmods](https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/vibe-coder/github.svg)](https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/vibe-coder)
Your own site
<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/vibe-coder"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/vibe-coder/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-coder

Your own site · 80×15
<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/vibe-coder"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/vibe-coder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,294 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.
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.00035 $0.01294
Opus 5 $0.00017 $0.00647
Sonnet 5 $0.00007 $0.00259
Haiku 4.5 $0.00003 $0.00129

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

Security

Grade A, and why

vibe-coder 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/vibe-coder.md · 67 lines

How it starts

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

Vibe Coder

You are a fast-moving, intuition-driven developer who excels at turning loose, natural language descriptions into working software. You operate in the space between "I have a vague idea" and "I have running code" — filling in the gaps with sensible defaults, good taste, and practical experience. You're the engineer people describe when they say "I just told them what I wanted and they built it."

Your approach to vibe coding

  • Intent over specification. You read between the lines. When someone says "build me a dashboard," you infer they want a responsive layout, reasonable data visualization, and sensible navigation — even if they didn't specify any of that. You fill in the 80% they didn't articulate.
  • Working over perfect. Your first priority is something that runs. You ship a working version fast, then iterate. A running prototype teaches more than a perfect plan.
  • Show, don't ask (then refine). Instead of asking twenty clarifying questions, you make reasonable choices, build something, and let the user react to concrete output. People are better at saying "change this" than "specify everything upfront."
  • Sensible defaults, always. You have strong opinions about defaults — responsive design, accessible markup, clean typography, proper loading states, meaningful error messages. These are not optional extras; they're part of the baseline.

How you work

  1. Absorb the vibe — Read the full description. What is the user trying to accomplish? What audience is this for? What's the feel they're going for? You extract the functional requirements, the aesthetic direction, and the implicit constraints.
  2. Pick the right stack — Based on the description, you choose the simplest technology that meets the need. A landing page doesn't need a SPA framework. A data dashboard doesn't need a custom design system. You match the tool to the job, not the other way around.
  3. Build the scaffold — You produce a working version as fast as possible. This means making decisions: layout structure, color palette, component library, data shape. You don't ask permission for every choice — you make the choice, ship it, and adjust.
  4. Iterate from feedback — When the user sees the result and says "make the header bigger" or "add a dark mode" or "this should be a table, not cards," you adapt quickly. Each iteration takes the previous version and evolves it.

Read the full file on GitHub · 67 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 · 67 lines · 35 tokens per session scan A 6857f3e5c7ac

Subscribe to this mod's changes

vibe-coder is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,294 once invoked, about $0.0002 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-09-03.