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 zhu1090093659/spec_driven_developnpx agentmods add plugins/zhu1090093659/spec_driven_develop/spec-driven-developgit clone --depth 1 https://github.com/zhu1090093659/spec_driven_developGrade A, and why
spec-driven-develop 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": "spec-driven-develop",
"displayName": "Spec-Driven Develop",
"version": "1.15.0",
"description": "Three complementary AI agent skills: (1) Spec-Driven Develop — automates full development workflow for large-scale complex tasks: project analysis, task decomposition, project governance, progress tracking, and execution; (2) Deep Discuss — structured deep discussion for problem analysis, brainstorming, and solution design; (3) Review SPD — findings-first code review for uncommitted changes, date-range commits, and branch/PR diffs.",
"author": {
"name": "zhu1090093659",
"url": "https://github.com/zhu1090093659"
},
"homepage": "https://github.com/zhu1090093659/spec_driven_develop",
"repository": "https://github.com/zhu1090093659/spec_driven_develop",
"license": "MIT",
"keywords": [
"spec-driven",
"workflow",
"planning",
"task-decomposition",
"project-analysis",
"deep-discuss",
"brainstorming",
"problem-analysis",
"code-review",
"review-spd",
"bug-risk"
],
"skills": "./skills/",
"agents": [
"./agents/project-analyzer.md",
"./agents/task-architect.md",
"./agents/task-executor.md",
"./agents/code-reviewer.md"
]
}
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 · 34 lines scan A ce8b634e9b70
spec-driven-develop is a plugin published in the GitHub repository zhu1090093659/spec_driven_develop (977 stars, last pushed 1mo 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
Spec-first workflow: integrates OpenSpec planning engine + Superpowers execution discipline. 9 collaborative skills with embedded TDD, SDD, code review, debugging, and delta spec sync.
spec-superflow
Spec-first workflow: integrates OpenSpec planning engine + Superpowers execution discipline. 9 collaborative skills with embedded TDD, SDD, code review, debugging, and delta spec sync.
cavekit-marketplace
Cavekit — compressed spec-driven development for Claude Code.
ck
Cavekit — compressed spec-driven dev. Full loop (grill → spec → research → review → build) over one SPEC.md file: three core commands + four reach-for. Caveman encoding. Bug-to-spec backprop.
racecraft-plugins-public
Plugin marketplace listing 1 plugin: speckit-pro.
speckit-pro
Autonomous Spec-Driven Development powered by GitHub SpecKit. Includes archive-aware autopilot startup, SDD coaching, multi-spec project management, and a fully autonomous workflow executor with multi-agent clarification consensus.