vibe-spec

A plugin package containing the Vibe-Spec specification workflow and its full-stack development references. It includes commands for drafting, refining, planning, implementing, setup, diagnosis, troubleshooting, and secret checks.

In plain words
What is it for?
Use it to create and implement web-app specifications, prepare the development environment, troubleshoot failures, audit browser-exposed secrets, and consult references for the supported web stack.
Why use it?
It organizes project planning and common development checks in one reusable add-on.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add Connorrmcd6/vibe-spec
agentmods
npx agentmods add plugins/connorrmcd6/vibe-spec/vibe-spec
Clone the repo
git clone --depth 1 https://github.com/Connorrmcd6/vibe-spec

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 1 skill, 9 commands cost 531 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

vibe-spec 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 3d 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.

.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "vibe-spec",
  "description": "Spec-driven development workflow + a production-tested full-stack reference. A 5-step /spec-* workflow (draft, refine, phases, plan, implement) plus /spec-setup, /spec-doctor, and /spec-troubleshoot for environment setup, /spec-secrets for redacted secret-leak auditing, and a vibe-spec skill with 21 on-demand stack references (Next.js, Prisma, Auth, RBAC, dbt, CI/CD, secrets, doc governance, prerequisites, and more).",
  "version": "0.4.0",
  "author": {
    "name": "Connor McDonald",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/Connorrmcd6/vibe-spec",
  "repository": "https://github.com/Connorrmcd6/vibe-spec",
  "commands": "./commands",
  "skills": "./skills"
}
Contents

What it installs

The manifest is a name and a version. 1 skill, 9 commands travel with it, and installing the plugin installs all of them — 531 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Files

What ships with it

1 file beside plugin.json 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.

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. 3d ago First seen · 14 lines scan A 451462f81cb0

Subscribe to this mod's changes

vibe-spec is a plugin published in the GitHub repository Connorrmcd6/vibe-spec (9 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.