agentmods.dev

openspec-continue-change

openspec-continue-change is a skill for Claude Code from ValorVie/custom-skills. It costs 39 tokens per session (1,344 once invoked), scanned A, a copy of openspec-continue-change, MIT.

A workflow guide for continuing an OpenSpec change by creating its next required document or artifact.

In plain words
What is it for?
Use it to list active changes, select the intended one, inspect its progress, and create the next artifact in the change workflow.
Why use it?
It keeps planned software work moving in the correct order and prevents developers from choosing the wrong change or skipping required steps.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

not rated 5repo yesterday A scan 39 tokens copy · 86% MIT

Good fit Use it to list active changes, select the intended one, inspect its progress, and create the next artifact in the change workflow.

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

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/valorvie/custom-skills/openspec-continue-change/github.svg)](https://agentmods.dev/skills/valorvie/custom-skills/openspec-continue-change)
Your own site
<a href="https://agentmods.dev/skills/valorvie/custom-skills/openspec-continue-change"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/openspec-continue-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-continue-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/valorvie/custom-skills/openspec-continue-change"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/openspec-continue-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,344 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 86% 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.00039 $0.01344
Opus 5 $0.00019 $0.00672
Sonnet 5 $0.00008 $0.00269
Haiku 4.5 $0.00004 $0.00134

Measured 9d ago against content hash 329668263b60, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

openspec-continue-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

86% identical to openspec-continue-change — 45 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.

.agent/skills/openspec-continue-change/SKILL.md · 123 lines

How it starts

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

Continue working on a change by creating the next artifact.

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). 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: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

  1. If no change name provided, prompt for selection

    Run openspec list --json to get available changes sorted by most recently modified. Then use the AskUserQuestion tool to let the user select which change to work on.

    Present the top 3-4 most recently modified changes as options, showing:

    • Change name
    • Schema (from schema field if present, otherwise "spec-driven")
    • Status (e.g., "0/5 tasks", "complete", "no tasks")
    • How recently it was modified (from lastModified field)

    Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.

    IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.

  2. Check current status

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

    Parse the JSON to understand current state. The response includes:

    • schemaName: The workflow schema being used (e.g., "spec-driven")
    • artifacts: Array of artifacts with their status ("done", "ready", "blocked")
    • isComplete: Boolean indicating if all artifacts are complete
    • planningHome, changeRoot, artifactPaths, and actionContext: path and scope context. Use these instead of assuming repo-local paths.

  3. Act based on status:

    If all artifacts are complete (isComplete: true):

    • Congratulate the user
    • Show final status including the schema used
    • Suggest: "All artifacts created! You can now implement this change or archive it."
    • STOP

    If artifacts are ready to create (status shows artifacts with status: "ready"):

    • Pick the FIRST artifact with status: "ready" from the status output
    • Get its instructions: 
      openspec instructions <artifact-id> --change "<name>" --json
    • Parse the JSON. The key fields are:
      • context: Project background (constraints for you - do NOT include in output)
      • rules: Artifact-specific rules (constraints for you - do NOT include in output)
      • template: The structure to use for your output file
      • instruction: Schema-specific guidance
      • resolvedOutputPath: Resolved path or pattern to write the artifact
      • dependencies: Completed artifacts to read for context
    • Create the artifact file:
      • Read any completed dependency files for context
      • Use template as the structure - fill in its sections
      • Apply context and rules as constraints when writing - but do NOT copy them into the file
      • Write to the resolvedOutputPath specified in instructions. If it is a glob pattern, choose the concrete file path using the schema instruction and the change's context
    • Show what was created and what's now unlocked
    • STOP after creating ONE artifact

    If no artifacts are ready (all blocked):

    • This shouldn't happen with a valid schema
    • Show status and suggest checking for issues

  4. After creating an artifact, show progress

    openspec status --change "<name>"

Output

After each invocation, show:

  • Which artifact was created
  • Schema workflow being used
  • Current progress (N/M complete)
  • What artifacts are now unlocked
  • Prompt: "Want to continue? Just ask me to continue or tell me what to do next."

Read the full file on GitHub · 123 lines

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 · 123 lines · 39 tokens per session scan A 329668263b60

Subscribe to this mod's changes

openspec-continue-change is a skill published in the GitHub repository ValorVie/custom-skills (5 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,344 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to openspec-continue-change, differing in 45 lines, and is treated as a copy.

Claude CodePlanningai-assisted-developmentanthropicautomationclideveloper-experience
Related

Other skills, from other repositories

plan-growth-loop

Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".

SkeneTechnologies/skene · 45 tokens

validate-loop

Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".

SkeneTechnologies/skene · 43 tokens

c-calendar

View and create calendar events via gog (Google Calendar) or icalBuddy (Apple Calendar). Check availability, list upcoming events, create/update/delete events, and manage multiple calendars.

daxaur/openpaw · 39 tokens

c-contacts

Access macOS Contacts app via AppleScript. No CLI tool needed.

daxaur/openpaw · 21 tokens

c-jira

Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.

daxaur/openpaw · 45 tokens

c-lockin

Lock In Mode — orchestrate distraction blocking, environment setup, and session tracking.

daxaur/openpaw · 20 tokens