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 roedyrustam/vibes-plug --skill spec-driven-development-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/spec-driven-development-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/spec-driven-development-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/spec-driven-development-expert/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/roedyrustam/vibes-plug/spec-driven-development-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/spec-driven-development-expert.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.00076 | $0.03335 |
| Opus 5.5 | $0.00030 | $0.01334 |
| Sonnet 5.5 | $0.00015 | $0.00667 |
| Haiku 4.5 | $0.00008 | $0.00333 |
Grade A, and why
spec-driven-development-expert 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📐 Spec-Driven Development (SDD) & Contract-First Expert (2026 Edition)
English
Orchestration & Integration
- Upstream Specs & Discovery:
prd-architect,brainstorming,domain-driven-design-expert - Contract & Spec Tooling:
api-design-expert,openapi-swagger-codegen-expert,autonomous-api-drift-healer - Formal Verification & Typing:
formal-spec-z3-verifier,typescript-expert,structured-output-contracts - Testing & Verification:
autonomous-tdd-debugger,e2e-testing-expert,property-mutation-testing-expert - Backend Implementation:
js-backend-expert,database-orm-expert,anti-slop - Lifecycle & Governance:
zero-to-prod-orchestrator,session-memory-manager
Description
Spec-Driven Development (SDD) is the foundational engineering antidote to unstructured AI code generation. Instead of prompting AI agents to write code directly from vague conversational prompts, SDD enforces a strict Contract-First Lifecycle: formal, machine-readable specifications (TypeSpec, OpenAPI 3.1, JSON Schema Draft 2020-12, Gherkin BDD, and Pact Consumer-Driven Contracts) are authored, linted, and mathematically verified before any production code or test suite is generated.
This skill equips the AI agent to act as a Principal Specifications Architect, turning business requirements into unambiguous type-safe schemas, executable behavioral specifications, and automated contract drift verification pipelines.
Trigger Conditions
Activate this skill when:
- Designing new microservices, REST APIs, or full-stack application contracts.
- Defining cross-team or cross-agent API boundaries before parallel development.
- Preventing schema drift between frontend clients and backend services.
- Implementing Consumer-Driven Contract testing with Pact and Vitest.
- Authoring high-level modular API definitions using Microsoft TypeSpec (
tsp). - Translating PRD functional requirements into executable Gherkin behavioral scenarios (
.featurefiles).
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 Changed · +10 lines fc16e39b76b8
- 3d ago Changed · +1 lines 7bfd4678985d
- 6d ago Changed · +39 lines 4172d7703718
- 7d ago First seen · 336 lines · 76 tokens per session scan A c38c80768779
spec-driven-development-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (113 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 3,335 once invoked, about $0.0003 per session on Opus 5.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-10-17.
Other skills, from other repositories
ai-prompt-regression-testing
Use when comparing prompt changes against a fixed evaluation set: record actual model settings, required checks, missing results, judge limitations and case-level regression evidence.
ai-prompt-regression-testing
Prompt engineering regression test matrix register: baseline outputs, semantic drift thresholds, judge evaluations, and golden dataset.
test-gen
Generate test cases from type constraints and specs. Creates boundary tests, edge cases, and fixtures automatically. Pact-lang inspired. Triggers on: generate tests, test from spec, create fixtures, boundary tests.
generate-tests
Auto-generate Jest/Vitest test files with intelligent coverage and mock detection.
qa
QA Specialist Agent for smoke testing production deployments. Runs Playwright-based smoke tests against live URLs to verify health, auth flows, protected routes, and core UI. Use when validating a deploy, checking if a production app is working, or when asked to run QA on a project.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.