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.
/plugin marketplace add pe-menezes/vibeflownpx agentmods add plugins/pe-menezes/vibeflow/claude-codegit clone --depth 1 https://github.com/pe-menezes/vibeflowGrade A, and why
vibeflow 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 yesterday.
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": "vibeflow",
"version": "1.14.0",
"description": "Spec-driven development for AI agents. Define what to build, let the agent build it right. Vibeflow separates thinking from coding with specs, guardrails, and audits — grounded in your project's real patterns.",
"author": {
"name": "Pedro Menezes"
},
"repository": "https://github.com/pe-menezes/vibeflow-claude",
"license": "MIT",
"keywords": ["spec-driven", "architecture", "prompt-pack", "audit", "vibe-coding"]
}
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.
- yesterday First seen · 12 lines scan A 4b8761dc3f75
vibeflow is a plugin published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed 12d 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-30.
Other plugins, from other repositories
humanizer
Install Humanizer as a Claude plugin.
agent-toolkit
Plugin marketplace listing 4 plugins: agent-toolkit-core, agent-toolkit-agents, agent-toolkit-forge, agent-toolkit-craft.
agent-toolkit-complete
Full stable skill catalog coverage for consumers who want everything (.
threnody
Local-first MCP meta-harness: routes, plans, and swarms multi-agent coding work — emitting tier-aware Dynamic Workflows on Claude Code — while the host shell executes via Agent/Task subagents.
supply-chain-risk-auditor
Audit a project's npm, PyPI, and Go dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned upstreams, npm publisher concentration, and install scripts.
insecure-defaults
Detects insecure default configurations including hardcoded credentials, fallback secrets, weak authentication defaults, and dangerous values in production.