agentmods.dev

openspec-new-change

openspec-new-change is a skill for Claude Code from gustavo-meilus/aiboarding. It costs 40 tokens per session (875 once invoked), scanned A, a copy of openspec-new-change, MIT.

A workflow for starting an OpenSpec change, where a feature, fix, or modification is described through structured project artifacts.

In plain words
What is it for?
Use it to create a new change, select the appropriate OpenSpec store, and follow the artifact-based instructions for the requested work.
Why use it?
It gives development changes a consistent starting point and keeps the related specification work organized in the correct OpenSpec repository.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

Part of the aiboarding plugin — 17 skills, 11 commands, 4 hooks shipped together

not rated 2repo 12d ago A scan 40 tokens copy · 95% MIT

Good fit Use it to create a new change, select the appropriate OpenSpec store, and follow the artifact-based instructions for the requested work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gustavo-meilus/aiboarding/openspec-new-change
View source ↗ gustavo-meilus/aiboarding
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 gustavo-meilus/aiboarding --skill openspec-new-change
Clone the repo
git clone --depth 1 https://github.com/gustavo-meilus/aiboarding

Made for: Claude Code.

Or install aiboarding, the plugin that ships this one along with the rest of its 17 skills, 11 commands, 4 hooks.

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/gustavo-meilus/aiboarding/openspec-new-change/github.svg)](https://agentmods.dev/skills/gustavo-meilus/aiboarding/openspec-new-change)
Your own site
<a href="https://agentmods.dev/skills/gustavo-meilus/aiboarding/openspec-new-change"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/aiboarding/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.

agentmods 80×15 button for openspec-new-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/gustavo-meilus/aiboarding/openspec-new-change"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/aiboarding/openspec-new-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 875 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.
Origin 95% copy Near-identical to another mod 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.00040 $0.00875
Opus 5 $0.00020 $0.00438
Sonnet 5 $0.00008 $0.00175
Haiku 4.5 $0.00004 $0.00088

Measured 9d ago against content hash 66cc35916fde, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 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.

Origin

This is a copy

95% identical to openspec-new-change — 1 line 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.

.agents/skills/openspec-new-change/SKILL.md · 78 lines

What it actually says

Start a new change using the experimental artifact-driven approach.

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.

Steps

  1. If no clear input provided, ask what they want to build

    Ask the user (open-ended, no preset options):

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

  2. 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 --json and let them choose

    Otherwise: Omit --schema to use the default.

  3. Create the change directory

    openspec new change "<name>"

    Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change in the planning home resolved by the CLI.

  4. Show the artifact status

    openspec status --change "<name>" --json

    Use the returned planningHome, changeRoot, artifactPaths, and nextSteps instead of assuming repo-local paths.

  5. Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for 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.

  6. 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
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. 9d ago First seen · 78 lines · 40 tokens per session scan A 66cc35916fde

Subscribe to this mod's changes

openspec-new-change is a skill published in the GitHub repository gustavo-meilus/aiboarding (2 stars, last pushed 12d ago), licensed MIT. It adds 40 tokens to every session and 875 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to openspec-new-change, differing in 1 line, and is treated as a copy.

Claude CodePlanningProject managementagent-skillsagents-mdai-agentsautomationcodex
Related

Other skills, from other repositories

persona-event-coordinator

Plan and manage events — scheduling, invitations, and logistics.

googleworkspace/cli · 17 tokens

persona-project-manager

Coordinate projects — track tasks, schedule meetings, and share docs.

googleworkspace/cli · 17 tokens

persona-team-lead

Lead a team — run standups, coordinate tasks, and communicate.

googleworkspace/cli · 19 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

recipe-plan-weekly-schedule

Review your Google Calendar week, identify gaps, and add events to fill them.

googleworkspace/cli · 23 tokens

recipe-review-overdue-tasks

Find Google Tasks that are past due and need attention.

googleworkspace/cli · 18 tokens