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/maquina-app/rails-claude-code/spec-driven-developmentnpx skills add maquina-app/rails-claude-code --skill spec-driven-developmentgit clone --depth 1 https://github.com/maquina-app/rails-claude-codeWrote 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/maquina-app/rails-claude-code/spec-driven-development)<a href="https://agentmods.dev/skills/maquina-app/rails-claude-code/spec-driven-development"><img src="https://agentmods.dev/badge/skills/maquina-app/rails-claude-code/spec-driven-development.svg" alt="Measured on agentmods" 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 | $0.00099 | $0.03418 |
| Opus 5 | $0.00049 | $0.01709 |
| Sonnet 5 | $0.00020 | $0.00684 |
| Haiku 4.5 | $0.00010 | $0.00342 |
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 4d 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development
A lightweight workflow for building production-quality Rails features with AI agents through systematic planning and self-contained specs.
Each spec is designed to be picked up and executed independently by Claude Code or a subagent — no extra context needed beyond the spec folder itself.
Each phase is driven by a /sdd-* slash command (see the Commands table at the end). The phase sections below are the reference each command follows — read them when running a phase, whether the user typed the command or asked in natural language.
Quick Start
New Rails Project (from MVP docs):
/sdd-init— createssdd/with pre-built Rails standards + index/sdd-plan— convert MVP docs → product planning files- For each feature:
/sdd-shape→/sdd-tasks→ hand off to Claude Code
Adding Features to Existing App:
/sdd-init(if nosdd/yet)/sdd-discover-standards— capture patterns from the codebase/sdd-shape→/sdd-tasks→ hand off to Claude Code
Directory Structure
sdd/
├── product/
│ ├── mission.md # Product vision, users, problems
│ ├── roadmap.md # Feature priorities with effort estimates
│ └── tech-stack.md # Technology decisions and deviations
├── standards/
│ ├── index.yml # ← Catalog of all standards (auto-maintained)
│ ├── global/
│ │ └── rails-stack.md
│ ├── backend/
│ │ └── rails-patterns.md
│ ├── frontend/
│ │ ├── hotwire.md
│ │ └── components.md
│ └── testing/
│ └── minitest.md
└── specs/
└── YYYY-MM-DD-feature-name/
├── spec.md # Requirements, user stories, scope
├── references.md # Existing code to reuse/follow
├── standards.md # Standards that apply to THIS feature (injected from index)
└── tasks.md # Task groups with self-contained Claude Code prompts
Standards System
Standards are short .md files. Every word costs tokens — keep them concise and scannable.
What ships with it
3 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.
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.
- 4d ago First seen · 403 lines · 99 tokens per session scan A 8f3e14fdfb7c
spec-driven-development is a skill published in the GitHub repository maquina-app/rails-claude-code (47 stars, last pushed 19d ago), licensed MIT. It adds 99 tokens to every session and 3,418 once invoked, about $0.0005 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
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
growing-outside-in-systems
Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent…
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.