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 Vimalk0703/shipworthynpx agentmods add plugins/vimalk0703/shipworthy/marketplacegit clone --depth 1 https://github.com/Vimalk0703/shipworthyGrade A, and why
shipworthy marketplace 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 3d 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": "shipworthy",
"title": "Shipworthy",
"description": "Vibe coding is how you start; engineering is what keeps it alive. Auto-activating Claude Code plugin that silently installs production engineering guardrails — architecture awareness, TDD, quality gates, security-first development, and 25+ skills so vibe coders build real systems without thinking about process.",
"version": "1.0.0",
"author": "Vimal Kumar",
"repository": "https://github.com/Vimalk0703/shipworthy",
"categories": ["development", "architecture", "quality", "security"],
"platforms": ["claude-code", "cursor", "codex", "opencode"]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 3d ago First seen · 11 lines scan A ac276f93f3ea
shipworthy marketplace is a plugin published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 4mo 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
zuvo
Multi-agent skill ecosystem for structured software development. 57 skills and 26 specialized agents with quality gates, code exploration, and evidence-based review.
superpowers-zh
AI 编程超能力中文增强版：20 个 skills（14 翻译 + 4 中国原创 + 2 上游历史保留），支持 Claude Code / Hermes Agent / Cursor / Claw Code / Qoder 等 23 款工具.
antidote
Stop AI agents from patching symptoms. Forces structural root-cause fixes over symptom patching in any language or stack.
pdlc
Turn AI software engineering into an auditable, on-disk state machine. A staged PDLC workflow (PRD, design, TDD, implement, review, ship, retro) enforces hard contracts — artifacts on disk, per-feature state machine, tests-before-code, objective checks from real command exit codes, single-shot auto-repair — so AI work.
codoop-flow
In-session orchestration for the codoop-flow Agent-Centric ticket pipeline: pick -> build -> verify -> review -> ship, driven by a skill plus a deterministic guardrail CLI.
beast-forge
Plan iron, verify real. Ironclad planning with independent verification chain. Turns any input into a bulletproof plan, executes with TDD, verifies with independent agents.