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 krzysztofsurdy/code-virtuoso --skill spec-driven-developmentgit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/spec-driven-development)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/spec-driven-development"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/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/krzysztofsurdy/code-virtuoso/spec-driven-development"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/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.00057 | $0.02739 |
| Opus 5.5 | $0.00023 | $0.01096 |
| Sonnet 5.5 | $0.00011 | $0.00548 |
| Haiku 4.5 | $0.00006 | $0.00274 |
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 today.
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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-driven development
A spec is a file in the repo that says what to build and how to know it works. A plan says how. A task list says in what order. Writing them down lets a fresh session, a sub-agent, or a teammate pick up the work with no memory of the conversation that produced it. Chat history is lost at compaction and between sessions; files are not.
This playbook starts where brainstorming or a ticket ends: the idea is approved, and the question is how to build it. It does not explore vague ideas (use brainstorming) or drive a ticket through branch and PR (use ticket-delivery, which can call this playbook for its planning and execution phases).
Core principles
| Principle | Meaning |
|---|---|
| Scale the ceremony | A one-line fix does not need three documents. Pick the lightest artifact set that still lets a stranger finish the work. |
| Specs are files, not chat | Anything a later session needs goes in the repo. |
| Ambiguity blocks planning | Unresolved questions are marked in the spec and must be answered before the plan is written. |
| Every requirement is testable | Each has an ID and at least one WHEN/THEN criterion. If you cannot write the criterion, the requirement is not ready. |
| One task, one verified commit | A task is done when its check has run and passed, not when code exists. |
| Specs outlive the change | After merge, update the spec or archive it. A stale spec is worse than none. |
Step 0: Find the project's layout
Before creating anything, look for an existing convention and follow it:
| If the repo has | Use |
|---|---|
.specify/ or specs/<nnn-name>/ with spec.md, plan.md, tasks.md (GitHub Spec Kit) |
Spec Kit layout and templates |
.kiro/specs/<name>/ with requirements.md, design.md, tasks.md (Kiro) |
Kiro layout, EARS-style requirements |
openspec/ with specs/ and changes/ (OpenSpec) |
OpenSpec change folders and delta specs |
| None of these | specs/<slug>/spec.md, plan.md, tasks.md (default used below) |
What ships with it
6 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.
- today Changed · +6 lines 8f1aa77140cb
- 2d ago First seen · 161 lines · 57 tokens per session scan A c62aa20abbee
spec-driven-development is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 2,739 once invoked, about $0.0002 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-22.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
survey
A project-discovery workflow that creates `.claude/context.md`, a shared file describing the project's purpose, design, constraints, and measures of success.
dev-plan
Full development planning pipeline. Orchestrates a team of agents (researcher, prd-writer, software-architect, project-planner, issue-estimator) to take a project idea from concept to sprint-ready issues.
hermes-overnight-autonomy
Use for unattended Hermes continuity and watchdogs.
github-issues
Create, search, triage, and manage GitHub issues. Each section shows gh first, then the curl fallback.