openspec-new-change

openspec-new-change is a skill for Claude Code, Codex from redhat-developer/rhdh-skills. It costs 98 tokens per session (787 once invoked), scanned A, original, Apache-2.0.

A setup helper for OpenSpec, a system that organizes proposed software changes into structured documents. It creates a change folder and displays the template for the first document.

In plain words
What is it for?
Use it when starting or scaffolding an OpenSpec change, or when you need to know which document comes first.
Why use it?
It removes the need to remember the folder structure and setup commands before planning a change. It stops before writing proposal content.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the refinement plugin — 13 skills shipped together

Good fit Use it when starting or scaffolding an OpenSpec change, or when you need to know which document comes first.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/redhat-developer/rhdh-skills/openspec-new-change
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.

Any agent
npx skills add redhat-developer/rhdh-skills --skill openspec-new-change
Clone the repo
git clone --depth 1 https://github.com/redhat-developer/rhdh-skills

Made for: Claude Code, Codex.

Or install refinement, the plugin that ships this one along with the rest of its 13 skills.

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-new-change

README.md
[![agentmods](https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-new-change.svg)](https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-new-change)
Your own site
<a href="https://agentmods.dev/skills/redhat-developer/rhdh-skills/openspec-new-change"><img src="https://agentmods.dev/badge/skills/redhat-developer/rhdh-skills/openspec-new-change.svg" alt="Measured on agentmods" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 787 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00098 $0.00787
Opus 5 $0.00049 $0.00394
Sonnet 5 $0.00020 $0.00157
Haiku 4.5 $0.00010 $0.00079

Measured 8d ago against content hash 7ffae42f752f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

openspec-new-change 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 8d 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.

skills/refinement/openspec-new-change/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Start a new OpenSpec change

Scaffold a change directory and hand the caller the first artifact's template, then stop — drafting content is a separate turn.

Steps

  1. Ensure the project schema is installed. Check whether openspec/config.yaml and openspec/schemas/rhdh-spec-driven/ already exist. Only if either is missing, invoke /rhdh-spec-driven-schema and run its project-install step. Then confirm with openspec schemas --json that rhdh-spec-driven is listed.

  2. Get the change name. If the user's request already names it or describes what they want to build, derive a kebab-case name (e.g. "add user authentication" -> add-user-auth). Otherwise ask what they want to build or fix; do not proceed without knowing.

  3. Pick the schema. Prefer rhdh-spec-driven (now on disk). Pass --schema rhdh-spec-driven, or omit --schema to take the configured default from openspec/config.yaml. If the user names another available schema from openspec schemas --json, use that instead.

  4. Create the change directory:

    openspec new change "<name>" [--schema <name>]
    

    This scaffolds openspec/changes/<name>/ with the selected schema.

  5. Show status:

    openspec status --change "<name>"
    
  6. Get the first artifact's instructions. Find the first artifact with status: "ready" in the status output (schema-dependent — proposal for rhdh-spec-driven), then:

    openspec instructions <first-artifact-id> --change "<name>" --json
    

    Read /rhdh-spec-driven-schema for what the context, rules, and template fields in that response mean before summarizing them.

  7. Stop and wait for user direction.

Output

Summarize: change name and location, schema and its artifact sequence (proposal -> {specs, design} -> tasks for rhdh-spec-driven — specs and design are siblings that each depend only on proposal), current status (0/N artifacts complete), and the template for the first artifact. Close with: "Ready to create the first artifact? Describe what this change is about and I'll draft it, or ask me to continue."

Read the full file on GitHub · 80 lines

Files

What ships with it

1 file 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.

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. 8d ago First seen · 80 lines · 98 tokens per session scan A 7ffae42f752f

Subscribe to this mod's changes

openspec-new-change is a skill published in the GitHub repository redhat-developer/rhdh-skills (16 stars, last pushed 4d ago), licensed Apache-2.0. It adds 98 tokens to every session and 787 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens