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.
git clone --depth 1 https://github.com/Connorrmcd6/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/plugins/connorrmcd6/vibe-spec/vibe-spec)<a href="https://agentmods.dev/plugins/connorrmcd6/vibe-spec/vibe-spec"><img src="https://agentmods.dev/badge/plugins/connorrmcd6/vibe-spec/vibe-spec/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/plugins/connorrmcd6/vibe-spec/vibe-spec"><img src="https://agentmods.dev/badge/plugins/connorrmcd6/vibe-spec/vibe-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 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
{
"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"
}
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.
- Skill vibe-spec A 109 tokens
- Command spec-plan A 49 tokens
- Command spec-phases A 35 tokens
- Command spec-secrets A 57 tokens
- Command spec-doctor A 51 tokens
- Command spec-implement A 36 tokens
- Command spec-refine A 49 tokens
- Command spec-setup A 55 tokens
- Command spec-draft A 40 tokens
- Command spec-troubleshoot B 50 tokens
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.
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 · 14 lines scan A 451462f81cb0
vibe-spec is a plugin published in the GitHub repository Connorrmcd6/vibe-spec (9 stars, last pushed 3mo 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.
Other plugins, from other repositories
inbox-zero-api
Use the Inbox Zero API CLI (inbox-zero-api) from Cursor: rules, stats, OpenAPI schema, and safe mutations. Same skill source as OpenClaw / ClawHub (clawhub/inbox-zero-api).
statecore marketplace
Plugin marketplace listing 1 plugin: statecore.
statecore
Auditable project memory for Claude Code: captures every prompt and reply into StateCore, re-injects the project's memory at session start and after compaction, and exposes the remember/recall/facts/why/forget/handoff tools.
todox
The log your next session resumes from: decisions, dead ends, handoffs and open tasks, shared across machines, agents and people over the todox MCP server. Reminds a session to read the log first and to write it up before finishing.
superpowers-gstack
Routing, context management, and project setup for the Superpowers + GStack workflow.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.