What is source-command-opsx-propose?

A command that creates a new OpenSpec change, a documented software change, together with its proposal, design, and task list.

Use it to turn a feature or fix description into an implementation proposal, technical design, and ordered task list. Start coding afterward with the apply command.

It removes the need to create the change folder and planning documents separately before implementation.

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-propose/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-propose/github.svg)](https://agentmods.dev/skills/killin0415/memoir/source-command-opsx-propose)

Your own site

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

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

When invoked 1,014 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 81% 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.00023	$0.01014
Opus 5.5	$0.00009	$0.00406
Sonnet 5.5	$0.00005	$0.00203
Haiku 4.5	$0.00002	$0.00101

Measured 1mo ago against content hash c8497ebbe952, 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-propose 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

81% identical to openspec-ff-change — 39 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-propose/SKILL.md · 111 lines

How it starts

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

source-command-opsx-propose

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

Command Template

Propose a new change - create the change and generate all artifacts in one step.

I'll create a change with artifacts:

proposal.md (what & why)
design.md (how)
tasks.md (implementation steps)

When ready to implement, run /opsx:apply

Input: The argument after /opsx:propose is the change name (kebab-case), OR a description of what the user wants to build.

Steps

If no 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.
Create the change directory
```
openspec new change "<name>"
```
This creates a scaffolded change at openspec/changes/<name>/ with .openspec.yaml.
Get the artifact build order
```
openspec status --change "<name>" --json
```
Parse the JSON to get:
- applyRequires: array of artifact IDs needed before implementation (e.g., ["tasks"])
- artifacts: list of all artifacts with their status and dependencies
Create artifacts in sequence until apply-ready

Use the TodoWrite tool to track progress through the artifacts.

Loop through artifacts in dependency order (artifacts with no pending dependencies first):

a. For each artifact that is ready (dependencies satisfied):
- Get instructions:
```
openspec instructions <artifact-id> --change "<name>" --json
```
- The instructions JSON includes:
  - 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 for this artifact type
  - outputPath: Where to write the artifact
  - dependencies: Completed artifacts to read for context
- Read any completed dependency files for context
- Create the artifact file using template as the structure
- Apply context and rules as constraints - but do NOT copy them into the file
- Show brief progress: "Created "

Read the full file on GitHub · 111 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 · 111 lines · 23 tokens per session scan A c8497ebbe952

Subscribe to this mod's changes

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

Planning

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

systematic-debugging

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

obra/superpowers · 21 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

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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.