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/muyen/vibe-to-prodWrote 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/muyen/vibe-to-prod/vibe-to-prod-skills)<a href="https://agentmods.dev/plugins/muyen/vibe-to-prod/vibe-to-prod-skills"><img src="https://agentmods.dev/badge/plugins/muyen/vibe-to-prod/vibe-to-prod-skills/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/muyen/vibe-to-prod/vibe-to-prod-skills"><img src="https://agentmods.dev/badge/plugins/muyen/vibe-to-prod/vibe-to-prod-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibe-to-prod-skills 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 12d 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-to-prod-skills",
"description": "Production-ready skills including ralph-invoke (Claude-initiated autonomous loops), code-review, dev-workflow, git-workflow, security-scan, and more",
"source": "./",
"strict": false,
"skills": [
"./.claude/skills/ralph-invoke",
"./.claude/skills/code-review",
"./.claude/skills/continuous-improvement",
"./.claude/skills/dev-workflow",
"./.claude/skills/git-workflow",
"./.claude/skills/openapi-workflow",
"./.claude/skills/security-scan",
"./.claude/skills/systematic-debugging"
]
}What it installs
The manifest is a name and a version. 8 skills travel with it, and installing the plugin installs all of them — 193 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#vibe-to-prod-skills 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.
- 12d ago First seen · 16 lines scan A 9fca10b71035
vibe-to-prod-skills is a plugin published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo 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-10-04.
Other plugins, from other repositories
cadence
A plan/execute/verify loop for a single developer in Claude Code, with adversarial review at every gate: plans and diffs get refuted by a fresh Claude subagent or a panel of outside models (OpenAI, Gemini, DeepSeek), not just approved. State lives in files, not the conversation, so you clear aggressively and keep both.
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
aigon
aigon. Aigon is a local, open-source, spec-first software-delivery orchestrator for coding agents. It takes a Git-backed feature spec through isolated implementation, cross-agent review, and merge—using the agents and subscriptions you already have.
workflow
Code review and worktree workflow commands.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
forgedock
Autonomous AI development pipeline that uses GitHub as a structured knowledge graph for Claude Code agents. Adds /work-on, /review-pr, /quality-gate, /orchestrate, and 20+ pipeline commands.