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 ArabelaTso/Skills-4-SE --skill specification-driven-generationgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/specification-driven-generation)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/specification-driven-generation"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/specification-driven-generation/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/arabelatso/skills-4-se/specification-driven-generation"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/specification-driven-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01950 |
| Opus 5 | $0.00032 | $0.00975 |
| Sonnet 5 | $0.00013 | $0.00390 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
specification-driven-generation 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 7d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification-Driven Generation
Generate implementation code and validation tests from written specifications through a systematic specification-to-code workflow.
Workflow
1. Analyze Specification
Read and extract requirements from the specification:
- Identify functional requirements (what the code must do)
- Extract input/output contracts (parameters, return types, constraints)
- Note edge cases, error conditions, and validation rules
- Understand performance requirements or complexity constraints
- Identify data structures and algorithms needed
2. Design Implementation
Plan the code structure before writing:
- Choose appropriate data structures
- Select efficient algorithms
- Plan class/function organization
- Identify helper functions needed
- Consider error handling approach
3. Generate Implementation
Write clean, well-documented code that satisfies the specification:
Code Structure:
- Use clear, descriptive names that reflect the specification
- Add docstrings/comments explaining the specification being implemented
- Include type hints/annotations where applicable
- Implement all required functionality
- Handle edge cases and errors per specification
Common Patterns:
- Data structures: Classes with proper encapsulation, initialization, and methods
- Algorithms: Step-by-step implementation with complexity documentation
- Validators: Input validation matching specification constraints
- Utilities: Helper functions for complex operations
4. Generate Tests
Create comprehensive tests that validate the implementation against the specification:
Test Coverage:
- Normal cases from specification examples
- Edge cases mentioned in specification
- Error cases and validation rules
- Boundary conditions
- Performance requirements (if specified)
Test Structure:
# Example: Testing a sorted list data structure
def test_basic_functionality():
# From spec: "Insert elements in sorted order"
sl = SortedList()
sl.insert(5)
sl.insert(2)
sl.insert(8)
assert sl.to_list() == [2, 5, 8]
def test_edge_case_duplicates():
# From spec: "Allow duplicate elements"
sl = SortedList()
sl.insert(3)
sl.insert(3)
assert sl.to_list() == [3, 3]
def test_error_handling():
# From spec: "Raise TypeError for non-comparable items"
sl = SortedList()
with pytest.raises(TypeError):
sl.insert("string")
sl.insert(5)
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.
- 7d ago First seen · 322 lines · 64 tokens per session scan A 1a5233a64dfb
specification-driven-generation is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (251 stars, last pushed 20d ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,950 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
702-technologies-wiremock
Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot…
321-frameworks-spring-boot-testing-unit-tests
Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test…
flake-triage
Decide whether a preview the visual-diff bot flagged actually regressed or is simply nondeterministic, using a repeat-render oracle at a single commit. Use when a PR's preview diff reports a changed preview whose source the PR does not touch, or when a render, GIF or filmstrip is suspected of being unstable.
codex-qa
QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real /.codex. The first-party method drives the real codex app-server against an isolated CODEXHOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by…
refactor-safely
Restructure existing code safely without changing externally observable behavior. Composes context, design, architecture, code quality, and testing guardrails into a characterization-first refactoring workflow. Use when the user says 'refactor this', 'clean this up', 'untangle this module', 'move this to the right…
wio
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health. Use for prompts about what to test next, adding or improving tests, reviewing whether a test is worth keeping, low-signal or flaky tests…