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.
npx agentmods add skills/zhu1090093659/spec_driven_develop/spec-driven-developnpx skills add zhu1090093659/spec_driven_develop --skill spec-driven-developgit clone --depth 1 https://github.com/zhu1090093659/spec_driven_developWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00148 | $0.04551 |
| Opus 5 | $0.00074 | $0.02276 |
| Sonnet 5 | $0.00030 | $0.00910 |
| Haiku 4.5 | $0.00015 | $0.00455 |
Grade 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Develop
You are executing the Spec-Driven Development workflow — a seven-phase pipeline (Phases 0-6) for large-scale complex tasks. Complete preparation phases (analysis, planning, progress setup), then execute the plan — all within a single session.
Behavioral rules: references/behavioral-rules.md — read and follow them in every phase; they are non-negotiable.
Configuration
| Path | Default Value | Purpose |
|---|---|---|
| Analysis output | docs/analysis/ |
Phase 1 analysis documents |
| Plan output | docs/plan/ |
Phase 3 planning documents |
| Progress output | docs/progress/ |
Phase 4 tracking documents (incl. MASTER.md) |
| Instruction surfaces | Resolved per project | Project-level constraints for agents (see Phase 4) |
| Memory surface | Native first | Durable facts via the agent's native memory when available; repo fallback only when explicitly selected |
| Archive output | docs/archives/<project>/ |
Phase 6 archived artifacts |
| Task tracking mode | Auto-detect | GITHUB_FULL, GITHUB_STANDARD, or LOCAL_ONLY |
| Delivery batching | Phase-first | Issues track tasks; PRs integrate coherent task batches |
| Adaptive control | Enabled | Drift thresholds: annotate=20%, replan=40%, rescope=60% of phase tasks |
Canonical references (each topic has exactly one home — cite it, never re-explain it):
| Reference | Owns |
|---|---|
references/behavioral-rules.md |
All behavioral rules (1-19) |
references/github-integration.md |
Tracking modes, pre-flight check, all gh commands and Issue/PR body templates |
references/adaptive-control.md |
Telemetry collection, drift calculation, response actions, state storage, controller activation |
references/parallel-protocol.md |
Dispatch/review admission (tiers), lane/worktree protocol, review loop, merge risk, post-integration checks |
references/super-philosophy.md |
S.U.P.E.R principles + the 10-check review checklist |
references/templates/ |
Schemas for every generated document (analysis, plan, progress, governance, archive) |
What ships with it
10 files beside SKILL.md 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.
- references/adaptive-control.md 9.2 KB
- references/behavioral-rules.md 7.0 KB
- references/github-integration.md 15 KB
- references/parallel-protocol.md 9.3 KB
- references/super-philosophy.md 5.7 KB
- references/templates/analysis.md 5.2 KB
- references/templates/archive.md 1.7 KB
- references/templates/governance.md 3.2 KB
- references/templates/plan.md 6.4 KB
- references/templates/progress.md 7.2 KB
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.
- 2d ago First seen · 250 lines · 148 tokens per session scan A 53861b7fd946
spec-driven-develop is a skill published in the GitHub repository zhu1090093659/spec_driven_develop (976 stars, last pushed 1mo ago), licensed MIT. It adds 148 tokens to every session and 4,551 once invoked, about $0.0007 per session on Opus 5. 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 skills, from other repositories
build-executor
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
workflow-start
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/ /, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out…
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
contract-builder
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.
spec-writer
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.