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/Habib0x0/spec-driven-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/habib0x0/spec-driven-plugin/spec-driven-plugin)<a href="https://agentmods.dev/plugins/habib0x0/spec-driven-plugin/spec-driven-plugin"><img src="https://agentmods.dev/badge/plugins/habib0x0/spec-driven-plugin/spec-driven-plugin/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/habib0x0/spec-driven-plugin/spec-driven-plugin"><img src="https://agentmods.dev/badge/plugins/habib0x0/spec-driven-plugin/spec-driven-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
spec-driven 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
{
"name": "spec-driven",
"version": "5.3.3",
"description": "Spec-driven development workflow with structured requirements, design, and task phases",
"author": {
"name": "habib0x"
},
"keywords": ["specs", "requirements", "design", "planning", "workflow", "EARS"],
"agents": [
"./agents/spec-planner.md",
"./agents/spec-tasker.md",
"./agents/spec-validator.md",
"./agents/spec-implementer.md",
"./agents/spec-tester.md",
"./agents/spec-reviewer.md",
"./agents/spec-consultant.md",
"./agents/spec-acceptor.md",
"./agents/spec-documenter.md",
"./agents/spec-scanner.md",
"./agents/spec-debugger.md"
],
"commands": [
"./commands/spec.md",
"./commands/spec-brainstorm.md",
"./commands/spec-refine.md",
"./commands/spec-tasks.md",
"./commands/spec-status.md",
"./commands/spec-validate.md",
"./commands/spec-exec.md",
"./commands/spec-loop.md",
"./commands/spec-accept.md",
"./commands/spec-docs.md",
"./commands/spec-release.md",
"./commands/spec-verify.md",
"./commands/spec-retro.md",
"./commands/spec-complete.md",
"./commands/research.md",
"./commands/zoom-out.md",
"./commands/ubiquitous-language.md"
]
}
What it installs
The manifest is a name and a version. 1 skill, 18 commands, 11 agents travel with it, and installing the plugin installs all of them — 1,959 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill spec-workflow A 92 tokens
- Command spec A 12 tokens
- Command spec-brainstorm A 18 tokens
- Command spec-retro A 15 tokens
- Command spec-release A 13 tokens
- Command spec-status A 10 tokens
- Command spec-validate A 9 tokens
- Command spec-verify A 14 tokens
- Command ubiquitous-language A 36 tokens
- Command spec-bugfix A 20 tokens
- Command spec-refine A 13 tokens
- Command spec-tasks A 13 tokens
- Command spec-exec A 14 tokens
- Command spec-complete A 19 tokens
- Command research A 29 tokens
- Command spec-accept A 15 tokens
- Command spec-docs A 12 tokens
- Command zoom-out A 18 tokens
- Command spec-loop B 11 tokens
- Agent spec-debugger A 25 tokens
- Agent spec-planner A 287 tokens
- Agent spec-scanner A 41 tokens
- Agent spec-tester A 33 tokens
- Agent spec-tasker A 279 tokens
- Agent spec-acceptor A 251 tokens
- Agent spec-documenter A 100 tokens
- Agent spec-validator A 275 tokens
- Agent spec-consultant A 228 tokens
- Agent spec-reviewer A 29 tokens
- Agent spec-implementer A 28 tokens
What ships with it
1 file beside plugin.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 · 42 lines scan A e83b644c3e6e
spec-driven is a plugin published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 5mo 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
wyx
Architecture guardrails for Claude Code — automatically injects declared module boundaries into Claude's context when it edits files near a spec.
capstone
Architecture reference generator: a lean docs/capstone/ index plus topic files stamped to the commit they were derived at, built and kept current by one command, map. Companion commands: doctor, an opt-in two-sided review, a greenfield pipeline from mockup to running code with a frontend-design stage, and a…
deep-plan
AI-assisted deep planning with research, interview, external LLM review, and TDD approach.
capstone
Architecture reference docs: a docs/capstone/ index plus topic files stamped to commits, built and kept current by one command, map, plus doctor/review, a greenfield pipeline from product mockup to running code with a frontend-design stage, and a doc-grounded feature chain.
punchcard
Architecture-level code review from a fifty-year veteran: design, boundaries, data and error paths — never naming or formatting. One verdict, every finding that earns its place, every claim demonstrated in code. Reviews a diff in the conversation or posts one review into a GitHub PR / GitLab MR. Briefs a change before.
dokmatiq-docgen
Document generation with stationery/letterhead overlay, e-invoicing (ZUGFeRD/XRechnung/Factur-X), Excel, PDF signing, and AI receipt recognition for Codex and Claude Code. Bundles the Dokmatiq DocGen MCP server (40 tools) with a triggering skill.