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 intent-driven-dev/intent-driven-template --skill spec-as-sourcegit clone --depth 1 https://github.com/intent-driven-dev/intent-driven-templateWrote 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/intent-driven-dev/intent-driven-template/spec-as-source)<a href="https://agentmods.dev/skills/intent-driven-dev/intent-driven-template/spec-as-source"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/intent-driven-template/spec-as-source/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/intent-driven-dev/intent-driven-template/spec-as-source"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/intent-driven-template/spec-as-source.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.00036 | $0.00739 |
| Opus 5.5 | $0.00014 | $0.00296 |
| Sonnet 5.5 | $0.00007 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
spec-as-source 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec As Source
Overview
Use OpenSpec spec.md files as the executable source of truth. When this skill is active, fenced-Gherkin authoring, acceptance-first task ordering, spec-first implementation, and BDD zone isolation are one workflow.
REQUIRED SUB-SKILL: Use gherkin-authoring when drafting or modifying fenced Gherkin.
REQUIRED SUB-SKILL: Use acceptance-test-authoring when configuring or modifying the acceptance runner, extractor, linting, step definitions, or page objects.
Activation
This workflow is opt-in. Apply it only when the user or project instructions explicitly require spec-as-source.
Once active, the BDD zone rules below are mandatory. Do not activate or disable zone isolation separately.
Artifact References
- When this skill is active, its artifact references override the corresponding templates from the configured OpenSpec schema.
- Draft each
spec.mdfrom references/spec.md, not fromopenspec/schemas/intent-driven/templates/spec.md. - Draft
tasks.mdfrom references/tasks.md, not from the schema task template, preserving acceptance-test-first ordering.
BDD Zone Rules
- Code is written only for an active change under
openspec/changes/whose scenarios describe the behavior. - A unit of work edits either the specs zone (non-
tasks.mdfiles underopenspec/) or the code zone (non-tasks.mdfiles outsideopenspec/), never both while changes are uncommitted. - Before crossing zones, finish and commit or stash the current zone.
- Never commit specs-zone files and code-zone files together.
- Any file named
tasks.mdis zone-neutral: it may be edited alongside and committed with either zone. Task updates do not select or cross a zone and do not require a separate commit or stash. - Never revert or discard user-owned changes without explicit permission.
Use git status --porcelain before editing. Ignore files named tasks.md when selecting the zone. Of the remaining changed paths, those under openspec/ select the specs zone; those outside it select the code zone. If only tasks.md files are changed, no zone is selected.
What ships with it
2 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 6d3cd7d210dd
- 1mo ago First seen · 60 lines · 36 tokens per session scan A ed399cfdbbf1
spec-as-source is a skill published in the GitHub repository intent-driven-dev/intent-driven-template (169 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 739 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
tdd
Test-first at pre-agreed seams — one test, one implementation, tracer-bullet red/green; independent expected values; substitutions only at the seam's boundary class; launch Phase 4 reference.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
test-driven-development
Test-driven development, or TDD, is a way to build software by writing a test that fails, adding the smallest code that makes it pass, and then cleaning up the code. These instructions require that process for features, bug fixes, refactors, and behavior changes.