Borrowing it
Nothing to install: this file belongs to utilitydelta/mcp-graph-engine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/utilitydelta/mcp-graph-engine/main/.claude/skills/vibe-coding/SKILL.mdgit clone --depth 1 https://github.com/utilitydelta/mcp-graph-engineWrote 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/utilitydelta/mcp-graph-engine/vibe-coding)<a href="https://agentmods.dev/skills/utilitydelta/mcp-graph-engine/vibe-coding"><img src="https://agentmods.dev/badge/skills/utilitydelta/mcp-graph-engine/vibe-coding/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/utilitydelta/mcp-graph-engine/vibe-coding"><img src="https://agentmods.dev/badge/skills/utilitydelta/mcp-graph-engine/vibe-coding.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.00045 | $0.02918 |
| Opus 5.5 | $0.00018 | $0.01167 |
| Sonnet 5.5 | $0.00009 | $0.00584 |
| Haiku 4.5 | $0.00005 | $0.00292 |
Grade A, and why
vibe-coding 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 2mo 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 — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Coding Mode - Orchestrator Protocol
This skill is activated explicitly. When active, you become an orchestrator - you coordinate work, not do it directly. Implementation happens in sub-agents with isolated contexts.
Your code will never be merged directly. The human will study your output and replay the solution themselves in the real codebase. See human-replay-manifesto.md for the philosophy.
Architecture: Orchestrator + Workers
┌─────────────────────────────────────────────────────────────┐
│ ORCHESTRATOR (you) │
│ - Lightweight coordination context │
│ - Reads/updates SESSION_STATE.md │
│ - Spawns researcher for upfront exploration │
│ - Plans phases from spec + research findings │
│ - Spawns implementer for each phase │
│ - Runs validation agents after each phase │
│ - Commits after each phase │
│ - Updates progress log │
└──────────────────────────┬──────────────────────────────────┘
│
┌──────────────────────┼──────────────────────┐
│ │ │
▼ ▼ ▼
┌─────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ vibe- │ │ vibe- │ │ validation │
│ researcher │ │ implementer │ │ agents │
│ │ │ │ │ │
│ Explores │ │ Does work │ │ design- │
│ codebase, │ │ in isolated │ │ conformance, │
│ gathers │ │ context │ │ integration- │
│ context │ │ │ │ validator, │
│ │ │ │ │ code-arch │
└─────────────┘ └─────────────────┘ └─────────────────┘
↓ ↓ ↓
Research Each phase After each
phase (once) of work phase
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 435 lines · 45 tokens per session scan A b7f9c3e5b720
vibe-coding is a skill published in the GitHub repository utilitydelta/mcp-graph-engine (6 stars, last pushed 9mo ago), licensed MIT. It adds 45 tokens to every session and 2,918 once invoked, about $0.0002 per session on Opus 5.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-31.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…