Borrowing it
Nothing to install: this file belongs to atman-33/openspec-for-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/atman-33/openspec-for-copilot/main/.github/skills/openspec-new-change/SKILL.mdgit clone --depth 1 https://github.com/atman-33/openspec-for-copilotWrote 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/atman-33/openspec-for-copilot/openspec-new-change)<a href="https://agentmods.dev/skills/atman-33/openspec-for-copilot/openspec-new-change"><img src="https://agentmods.dev/badge/skills/atman-33/openspec-for-copilot/openspec-new-change/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/atman-33/openspec-for-copilot/openspec-new-change"><img src="https://agentmods.dev/badge/skills/atman-33/openspec-for-copilot/openspec-new-change.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.00040 | $0.00658 |
| Opus 5 | $0.00020 | $0.00329 |
| Sonnet 5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
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 9d 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.
This is a copy
80% identical to openspec-new-change — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Start a new change using the experimental artifact-driven approach.
Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.
Steps
-
If no clear input provided, ask what they want to build
Use the AskUserQuestion tool (open-ended, no preset options) to ask:
"What change do you want to work on? Describe what you want to build or fix."
From their description, derive a kebab-case name (e.g., "add user authentication" →
add-user-auth).IMPORTANT: Do NOT proceed without understanding what the user wants to build.
-
Determine the workflow schema
Use the default schema (omit
--schema) unless the user explicitly requests a different workflow.Use a different schema only if the user mentions:
- A specific schema name → use
--schema <name> - "show workflows" or "what workflows" → run
openspec schemas --jsonand let them choose
Otherwise: Omit
--schemato use the default. - A specific schema name → use
-
Create the change directory
openspec new change "<name>"Add
--schema <name>only if the user requested a specific workflow. This creates a scaffolded change atopenspec/changes/<name>/with the selected schema. -
Show the artifact status
openspec status --change "<name>"This shows which artifacts need to be created and which are ready (dependencies satisfied).
-
Get instructions for the first artifact The first artifact depends on the schema (e.g.,
proposalfor spec-driven). Check the status output to find the first artifact with status "ready".openspec instructions <first-artifact-id> --change "<name>"This outputs the template and context for creating the first artifact.
-
STOP and wait for user direction
Output
After completing the steps, summarize:
- Change name and location
- Schema/workflow being used and its artifact sequence
- Current status (0/N artifacts complete)
- The template for the first artifact
- Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."
Guardrails
- Do NOT create any artifacts yet - just show the instructions
- Do NOT advance beyond showing the first artifact template
- If the name is invalid (not kebab-case), ask for a valid name
- If a change with that name already exists, suggest continuing that change instead
- Pass --schema if using a non-default workflow
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.
- 9d ago First seen · 75 lines · 40 tokens per session scan A 2325ae101993
openspec-new-change is a skill published in the GitHub repository atman-33/openspec-for-copilot (22 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 658 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to openspec-new-change, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
artifact-conventions
Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.