Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Connorrmcd6/vibe-spec/plugin install vibe-specWrote 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/commands/connorrmcd6/vibe-spec/spec-draft)<a href="https://agentmods.dev/commands/connorrmcd6/vibe-spec/spec-draft"><img src="https://agentmods.dev/badge/commands/connorrmcd6/vibe-spec/spec-draft/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/commands/connorrmcd6/vibe-spec/spec-draft"><img src="https://agentmods.dev/badge/commands/connorrmcd6/vibe-spec/spec-draft.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.00040 | $0.00440 |
| Opus 5.5 | $0.00016 | $0.00176 |
| Sonnet 5.5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
spec-draft 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 1mo 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.
What it actually says
You are running Step 1 of the Vibe-Spec spec-driven workflow: writing a V0
spec. Consult the vibe-spec skill
(${CLAUDE_PLUGIN_ROOT}/skills/vibe-spec/reference/00-workflow.md) for the full
methodology.
The goal of V0 is a rough first draft. It is intentionally tool-agnostic — do not choose frameworks, databases, or libraries yet. Capture what the product does and how users interact with it.
What to do
- If
$ARGUMENTS(the idea) is empty, ask the user for a one-line description of what they want to build. - Interview the user to fill in the essentials. Ask about, at minimum:
- The core problem the product solves and who it's for
- The exact user workflows — e.g. "user logs in with OTP, sees a dashboard; pages differ by role; the app ingests data from an external API on a schedule"
- Distinct user types / roles, if any
- External systems it talks to (webhooks in/out, third-party APIs, scheduled jobs)
- What "done" looks like for a first version Ask in small batches; don't overwhelm. Accept that the user won't know everything yet — that's fine for V0.
- Write the result to
docs/project-spec.mdwith a clear heading marking it as V0. Structure it as: product summary, user types, user workflows (the bulk), external integrations, and open questions you couldn't resolve.
Keep it high-level and readable. Do not map features to tools — that's
/spec-refine (Step 2). End by telling the user to run /spec-refine next.
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.
- 1mo ago First seen · 34 lines · 40 tokens per session scan A 66d4a5f5d2b4
spec-draft is a command published in the GitHub repository Connorrmcd6/vibe-spec (9 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 440 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 commands, from other repositories
cleanup-repo
When /cleanup-repo is invoked, immediately execute the following steps to analyze, organize, and clean up the repository structure when files are scattered and disorganized.
devops
When /devops is invoked, immediately execute the following steps to create, configure, or manage DevOps infrastructure, CI/CD pipelines, and deployment configurations.
magic-wand
When /magic-wand [issue description] is invoked, immediately execute the following steps to perform a comprehensive, expert-level analysis and fix when standard debugging approaches have failed.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
brainstorm
When /brainstorm [topic] is invoked, immediately execute the following steps to collaboratively brainstorm, enhance, and plan new features for the app through an iterative product management workflow.
clean-code
When /clean-code [target] is invoked, immediately execute the following steps to remove redundant code, unused variables, dead code, debug statements, and other technical debt.