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.
npx agentmods add plugins/ash1794/vibe-engineering/marketplace/plugin marketplace add ash1794/vibe-engineeringgit clone --depth 1 https://github.com/ash1794/vibe-engineeringGrade A, and why
vibe-plugins 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": "vibe-plugins",
"metadata": {
"description": "Marketplace for vibe-engineering plugins — engineering discipline skills for Claude Code and OpenAI Codex"
},
"owner": {
"name": "Ashwin K",
"email": "[email protected]"
},
"plugins": [
{
"name": "vibe-engineering",
"source": "./plugins/vibe-engineering",
"description": "38 engineering discipline skills — research, quality gates, testing patterns, deployment, learning, gap analysis, spec sync, and more. Extracted from real-world development.",
"version": "1.5.1",
"author": {
"name": "Ashwin K",
"email": "[email protected]"
},
"homepage": "https://github.com/ash1794/vibe-engineering",
"repository": "https://github.com/ash1794/vibe-engineering",
"license": "MIT",
"category": "development",
"keywords": [
"skills",
"engineering",
"quality",
"testing",
"debugging",
"deployment",
"tdd",
"code-review",
"best-practices",
"workflows",
"vibe-coding",
"discipline"
]
}
]
}
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 · 41 lines scan A 6ea71a59a250
vibe-plugins is a plugin published in the GitHub repository ash1794/vibe-engineering (10 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
.claude
cherry-assistant-builtin. AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs.
credyt
Set up and integrate Credyt — real-time billing infrastructure for AI products. Guides you through pricing discovery, product configuration, verification, and code integration.
credyt
Set up and integrate Credyt — real-time billing infrastructure for AI products. Guides you through pricing discovery, product configuration, verification, and code integration.
credyt-marketplace
Plugin marketplace listing 1 plugin: credyt.
google-plugins
Plugin marketplace listing 17 plugins: alloydb, alloydb-omni, bigtable, cloud-sql-mysql, cloud-sql-postgresql.
xcode-build-skills
A multi-skill plugin for benchmarking and optimizing Xcode builds, compile hotspots, project settings, and Swift Package Manager dependency overhead.