agentmods.dev

openspec-schema-authoring

openspec-schema-authoring is a skill for Claude Code, Codex from intent-driven-dev/openspec-schemas. It costs 52 tokens per session (659 once invoked), scanned A, original, MIT.

A workflow skill for creating or customizing OpenSpec schemas, which define how a project records and manages proposed changes. It creates the schema files and templates inside an OpenSpec repository.

In plain words
What is it for?
Use it to initialize a new OpenSpec workflow, copy an existing schema for customization, or validate the resulting repository structure.
Why use it?
It removes the need to design the schema structure and workflow files manually. It also helps choose between starting a new schema and adapting an existing one.

Skill for Claude CodeCodex

not rated 92 19d ago A scan 52 tokens original MIT
View the source file intent-driven-dev/openspec-schemas
Install

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.

agentmods
npx agentmods add skills/intent-driven-dev/openspec-schemas/openspec-schema-authoring
Any agent
npx skills add intent-driven-dev/openspec-schemas --skill openspec-schema-authoring
Clone the repo
git clone --depth 1 https://github.com/intent-driven-dev/openspec-schemas

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for openspec-schema-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/intent-driven-dev/openspec-schemas/openspec-schema-authoring.svg)](https://agentmods.dev/skills/intent-driven-dev/openspec-schemas/openspec-schema-authoring)
Your own site
<a href="https://agentmods.dev/skills/intent-driven-dev/openspec-schemas/openspec-schema-authoring"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/openspec-schemas/openspec-schema-authoring.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 659 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00052 $0.00659
Opus 5 $0.00026 $0.00329
Sonnet 5 $0.00010 $0.00132
Haiku 4.5 $0.00005 $0.00066

Measured today against content hash 3ace27a45153, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openspec-schema-authoring 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.

.codex/skills/openspec-schema-authoring/SKILL.md · 87 lines

What it actually says

Create or customize an OpenSpec workflow schema in this repository.

Goal: produce a repository-local schema folder under openspec/schemas/<schema-name>/ containing schema.yaml and templates/.

Steps

  1. Decide whether to initialize or fork

    • Use init for a brand-new schema.
    • Use fork to customize an existing schema (preferred when starting from a known workflow).

  2. Discover available schemas to fork

    openspec schemas --json

  3. Option A: Initialize a new schema

    openspec schema init <schema-name>

    Common flags:

    • --description "..." to describe the workflow
    • --artifacts "proposal,specs,design,tasks" to set artifact IDs
    • --default to set as project default
    • --no-default to skip the interactive default prompt

    Expected result: openspec/schemas/<schema-name>/schema.yaml and openspec/schemas/<schema-name>/templates/.

  4. Option B: Fork an existing schema

    openspec schema fork <source> [new-schema-name]

    Sources can be:

    • Repository-local schemas
    • Built-in upstream schemas provided by the CLI

    Expected result: openspec/schemas/<new-schema-name>/schema.yaml and openspec/schemas/<new-schema-name>/templates/.

  5. Edit schema internals

    Ensure:

    • artifacts[].id matches intended workflow sequence
    • artifacts[].requires matches dependencies
    • artifacts[].generates matches artifact output paths
    • Template files exist in openspec/schemas/<schema-name>/templates/ for each artifact

  6. Validate changed schemas (required)

    openspec schema validate <schema-name>

    This is the supported schema quality gate for OpenSpec CLI 1.3.1. Do not use openspec schema review; that command is not available in this CLI.

  7. Debug schema resolution if behavior is unexpected

    openspec schema which <schema-name>

Done Criteria

  • Schema exists under openspec/schemas/<schema-name>/.
  • schema.yaml and templates/ are both present.
  • openspec schema validate <schema-name> passes.

Guardrails

  • Prefer openspec schema fork over manual copying.
  • Keep schemas repository-local under openspec/schemas/.
  • Do not skip validation before considering work complete.
Changes

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.

  1. today First seen · 87 lines · 52 tokens per session scan A 3ace27a45153

Subscribe to this mod's changes

openspec-schema-authoring is a skill published in the GitHub repository intent-driven-dev/openspec-schemas (92 stars, last pushed 19d ago), licensed MIT. It adds 52 tokens to every session and 659 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.

OpenSpecPlanningProject managementaicodingarchitectural-decision-recordssddspec-driven-developmentspecdrivendevelopment
Related

Other skills, from other repositories

openspec-bulk-apply-change

Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.

intent-driven-dev/intent-driven-template · 30 tokens

spec-manager

Spec-driven project iteration workflow — L1 PRD → L2 Design → L3 Impl → Agent Task → Deploy, with human review gates at each layer. Pure local markdown storage, no MCP, no network. Use when the user invokes /spec-manager or asks for: new feature/PRD, technical design, implementation spec, agent task, iteration plan…

loki-ai-ch/spec-manager · 92 tokens

spec-manager

Spec-driven project iteration workflow: L1 PRD -> L2 Design -> L3 Impl -> Agent Task, with human review gates at each layer.

loki-ai-ch/spec-manager · 33 tokens

openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

intent-driven-dev/intent-driven-template · 40 tokens

openspec-archive-change

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

intent-driven-dev/intent-driven-template · 31 tokens

openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

atman-33/openspec-for-copilot · 31 tokens