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 skills add VoDaiLocz/kilo-kit-mcp --skill spec-driven-developmentgit clone --depth 1 https://github.com/VoDaiLocz/kilo-kit-mcpWrote 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/skills/vodailocz/kilo-kit-mcp/spec-driven-development)<a href="https://agentmods.dev/skills/vodailocz/kilo-kit-mcp/spec-driven-development"><img src="https://agentmods.dev/badge/skills/vodailocz/kilo-kit-mcp/spec-driven-development/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/skills/vodailocz/kilo-kit-mcp/spec-driven-development"><img src="https://agentmods.dev/badge/skills/vodailocz/kilo-kit-mcp/spec-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00066 | $0.00937 |
| Opus 5 | $0.00033 | $0.00468 |
| Sonnet 5 | $0.00013 | $0.00187 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
spec-driven-development 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development (SDD)
SDD is the professional standard for high-assurance, agentic software engineering in 2026. It reverses the traditional "code-first" approach, elevating specifications to the primary system artifact. By ensuring code is merely a verified expression of precise specs, we eliminate ambiguity, technical debt, and misaligned requirements.
Why SDD in 2026?
As AI agents become the primary contributors to codebases, the bottleneck has shifted from writing code to defining intent. SDD provides:
- Alignment: Ensures AI agents work on the exact problem identified by the human.
- Traceability: Every line of code can be traced back to an acceptance criterion in a spec.
- Verification: Specs serve as the "ground truth" for automated test suites and agent-based verification.
- Efficiency: Reduces the need for costly refactoring by catching logic errors at the specification phase rather than the production phase.
When to Use
- New Features: Implementing non-trivial functionality.
- System Design: Defining architecture, data flows, or API contracts.
- Refactoring: When changing existing systems where behavioral preservation is critical.
- Complex Logic: When business rules are nuanced and prone to ambiguity.
- Agent Orchestration: When directing multiple agents, specs act as the shared project language.
Core Workflow (The SDD Lifecycle)
- Idea → PRD: Iterate with an AI agent to clarify the problem, user value, and constraints.
- PRD → Spec: Translate the PRD into an executable feature specification using User Stories and Acceptance Scenarios.
- Spec → Implementation Plan: Derive the technical approach. Ensure every technical decision is explicitly traced to a requirement in the spec.
- Plan → Code Generation: Use the plan to generate, review, and integrate code.
- Feedback → Evolution: Feed production metrics, user behavior, and edge-case discoveries back into the spec to keep the system's "truth" updated.
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.
- 5d ago Changed scan B → A 29470dc30ee2
- 9d ago First seen · 98 lines · 66 tokens per session scan B 4bf4b48ac4cb
spec-driven-development is a skill published in the GitHub repository VoDaiLocz/kilo-kit-mcp (26 stars, last pushed 4d ago), licensed Apache-2.0. It adds 66 tokens to every session and 937 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
llm-structured-output
Get reliable JSON, enums, and typed objects from LLMs using responseformat, tooluse, and schema-constrained decoding across OpenAI, Anthropic, and Google APIs.
drizzle-orm-expert
Expert in Drizzle ORM for TypeScript — schema design, relational queries, migrations, and serverless database integration. Use when building type-safe database layers with Drizzle.
landing-page-generator
Generates high-converting Next.js/React landing pages with Tailwind CSS. Uses PAS, AIDA, and BAB frameworks for optimized copy/components (Heroes, Features, Pricing). Focuses on Core Web Vitals/SEO.
tdmcp-pipeline
Orchestrates the tdmcp feature team end-to-end: design/wireframe → build → integrate → QA → release. Use whenever the user wants to build, implement, develop, ship, or add one or more tdmcp features/tools/effects/controls/AI-prompts for TouchDesigner, or to run them through a coordinated design→develop→QA→deploy…
startcycle-graph-user
Use when a task needs a small, throwaway multi-agent fan-out (a couple of parallel workers plus a review pass) in ANY project, without the full /startcycle-graph contract — no .agents/graph.md bootstrap, no state.json schema, no persistent files. Model-tiered by role (opus plan, sonnet review, haiku or an external CLI…
memb-skill
BDB local-first long-term memory engine (memB). Use when querying, remembering, or adapting preferences, code architectures, and developer patterns across tasks.