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/jsegov/shipspec-claude-code-pluginWrote 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/jsegov/shipspec-claude-code-plugin/marketplace)<a href="https://agentmods.dev/plugins/jsegov/shipspec-claude-code-plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/jsegov/shipspec-claude-code-plugin/marketplace/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/jsegov/shipspec-claude-code-plugin/marketplace"><img src="https://agentmods.dev/badge/plugins/jsegov/shipspec-claude-code-plugin/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
shipspec-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 1mo 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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "shipspec-marketplace",
"version": "1.0.0",
"description": "ShipSpec: Spec-driven development for Claude Code. Ship bigger features with confidence.",
"owner": {
"name": "jsegov"
},
"plugins": [
{
"name": "shipspec",
"description": "Spec-driven development for Claude Code. Plan bigger features with persistent PRDs, technical designs, and implementation tasks that keep your AI coding agent on track across sessions.",
"version": "1.1.0",
"author": {
"name": "ShipSpec"
},
"source": {
"source": "url",
"url": "https://github.com/jsegov/shipspec-claude-code-plugin.git"
},
"category": "development",
"homepage": "https://github.com/jsegov/shipspec-claude-code-plugin",
"keywords": [
"planning",
"prd",
"design",
"tasks",
"agents",
"production",
"security",
"compliance",
"soc2",
"code-analysis"
]
}
]
}
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.
- 1mo ago First seen · 38 lines scan A 8e600c2ac306
shipspec-marketplace is a plugin published in the GitHub repository jsegov/shipspec-claude-code-plugin (21 stars, last pushed 9mo 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
spec-superflow
Lean spec workflow: direct or planned execution with evidence-based completion.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
sharp-edges
Identify error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes.
genesis-spec-kit
AI coding with intent — the end of vibe coding. A spec-driven pipeline for Claude Code that loops a five-lens audit to zero findings before code ships. It won't save you time or tokens; it saves you from slop. File-backed, no external services. Legacy (V2-era) edition.
constitution
Manage project constitution files - rules, best practices, patterns, and guardrails for LLM/coding agents.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.