vibe-stack

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.

Security

Grade A, and why

vibe-stack 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 2d 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.

plugins/vibe-stack/.claude-plugin/plugin.json · 27 lines

What it actually says

{
  "name": "vibe-stack",
  "description": "The full vibe-coding loop: scaffold an app or marketing site with a real design system, animate it with GSAP and a real motion system, replace the fake data with a real backend, unstick it when it breaks, strip the AI look, ship it, and demo it.",
  "version": "0.4.0",
  "keywords": [
    "vibe-coding",
    "nextjs",
    "design-system",
    "landing-page",
    "seo",
    "animation",
    "gsap",
    "scroll-animation",
    "motion-design",
    "deploy",
    "debugging",
    "prototype"
  ],
  "homepage": "https://github.com/OneWave-AI/open-agent-stack/tree/main/plugins/vibe-stack",
  "repository": "https://github.com/OneWave-AI/open-agent-stack",
  "license": "MIT",
  "author": {
    "name": "OneWave AI",
    "url": "https://www.onewave-ai.com"
  }
}

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.

Related

Other plugins, from other repositories