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/intent-driven-dev/intent-driven-template/spec-as-sourcenpx skills add intent-driven-dev/intent-driven-template --skill spec-as-sourcegit clone --depth 1 https://github.com/intent-driven-dev/intent-driven-templateWhat 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.00036 | $0.00632 |
| Opus 5 | $0.00018 | $0.00316 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
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 yesterday.
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 (
openspec/) or the code zone (everything else), never both while changes are uncommitted. - Before crossing zones, finish and commit or stash the current zone.
- Never commit
openspec/files and code-zone files together. - Any file named
tasks.mdis exempt and may be edited from either zone. - Never revert or discard user-owned changes without explicit permission.
Use git status --porcelain before editing. Non-tasks.md paths under openspec/ select the specs zone; other changed paths select the code zone.
Workflow
- Draft and validate the proposal and fenced-Gherkin delta specs.
- Commit or stash specs-zone work before touching code.
- Establish the failing acceptance scenario or pending step before implementation.
- Implement the smallest change that makes the scenario pass.
- Keep the effective acceptance suite green with no pending or undefined steps.
- Commit or stash code-zone work before returning to specifications for sync or archive.
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.
- yesterday 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 (121 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 632 once invoked, about $0.0002 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
mermaid
Create, validate, and repair Mermaid.js diagrams. Use when generating flowcharts, sequence, class, ER, state, or Gantt diagrams, or any visualization.
teach-me
Turn a 'teach me X' request into a single interactive HTML lesson, rendered Arcade-first, by emitting a lesson data model and assembling it with rp1 tooling.
artifact-templates
Agent-only canonical output templates for rp1 artifacts. Load when producing structured markdown to ensure format consistency and routing metadata.
deep-research
Autonomous deep research on codebases and technical topics with structured report output via map-reduce explorer architecture.
generate-user-docs
Synchronizes user-facing documentation with the current knowledge base through validate -> stale gate -> scan -> approval -> process orchestration.
markdown-preview
Generate browser-viewable HTML previews from markdown, plain text, and Mermaid diagrams. Auto-validates, styles, and opens in browser.