What is source-command-opsx-continue?

An experimental instruction set for continuing a named software change by creating its next project artifact. An artifact is a document or file produced during the change process.

Use it with the opsx-continue command to select a change, inspect its status, and create the next required artifact.

It helps continue work that was started earlier and ensures the current change and its progress are checked first.

How killin0415/memoir configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to killin0415/memoir. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/killin0415/memoir/main/.agents/skills/source-command-opsx-continue/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/killin0415/memoir

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/killin0415/memoir/source-command-opsx-continue/github.svg)](https://agentmods.dev/skills/killin0415/memoir/source-command-opsx-continue)

Your own site

<a href="https://agentmods.dev/skills/killin0415/memoir/source-command-opsx-continue"><img src="https://agentmods.dev/badge/skills/killin0415/memoir/source-command-opsx-continue/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/killin0415/memoir/source-command-opsx-continue"><img src="https://agentmods.dev/badge/skills/killin0415/memoir/source-command-opsx-continue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,144 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 75% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.01144
Opus 5.5	$0.00008	$0.00458
Sonnet 5.5	$0.00004	$0.00229
Haiku 4.5	$0.00002	$0.00114

Measured 1mo ago against content hash 9866a92f023f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

source-command-opsx-continue 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 1mo 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

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

.agents/skills/source-command-opsx-continue/SKILL.md · 119 lines

How it starts

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

source-command-opsx-continue

Use this skill when the user asks to run the migrated source command opsx-continue.

Command Template

Continue working on a change by creating the next artifact.

Input: Optionally specify a change name after /opsx:continue (e.g., /opsx:continue add-auth). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

Steps

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.
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
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 with /opsx:apply or archive it with /opsx:archive."
- 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
  - outputPath: Where 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 output path specified in instructions
- Show what was created and what's now unlocked
- STOP after creating ONE artifact

Read the full file on GitHub · 119 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.

1mo ago First seen · 119 lines · 21 tokens per session scan A 9866a92f023f

Subscribe to this mod's changes

source-command-opsx-continue is a skill published in the GitHub repository killin0415/memoir (5 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 1,144 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 75% identical to openspec-continue-change, differing in 89 lines, and is treated as a copy.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

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

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

memoir: Skill for Claude Code