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 benjaminthomas/spec-driven-devnpx agentmods add plugins/benjaminthomas/spec-driven-dev/marketplacegit clone --depth 1 https://github.com/benjaminthomas/spec-driven-devGrade A, and why
spec-driven-dev 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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "spec-driven-dev",
"description": "Turn planning conversations into parallel-executable specs, implement them batch-by-batch with review gates, verify against the real running app, and ship a PR — plus a portable SEO/GEO operations skill.",
"owner": {
"name": "benjaminbarnabas"
},
"plugins": [
{
"name": "spec-driven-dev",
"description": "Spec-driven feature pipeline (spec-create / spec-implement / spec-verify / spec-checkpoint / spec-ship) + generative-seo, a portable SEO/GEO skill for any project.",
"source": "./",
"category": "productivity"
}
]
}
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.
- yesterday First seen · 17 lines scan A d3a5bf0ef4bd
spec-driven-dev is a plugin published in the GitHub repository benjaminthomas/spec-driven-dev (1 stars, last pushed 28d 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
funnel
Cross-channel marketing analytics across 600+ connectors.
funnel
Connect your AI agent to Funnel marketing data to compare cross-channel performance, track pacing, and analyze campaigns.
promptpilot
PromptPilot — turn rough, vague prompts into precise, context-enriched prompts inside your agent session.
vibelens
Gives Claude eyes on localhost. Captures a screenshot, console/network errors and a token-optimized DOM snapshot of your dev server so UI bugs get fixed from evidence instead of guesswork.
sync-agents-settings
Plugin marketplace listing 1 plugin: sync-agents-settings.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.