What is source-command-opsx-verify?

A verification workflow for checking that an implementation matches its change documents, such as specifications, task lists, and design decisions, before those documents are archived.

Use it to choose an OpenSpec change, inspect its workflow status and artifacts, and verify that the completed implementation matches the documented requirements.

It helps catch missing or inconsistent implementation work before a change is closed. It also requires selecting the change explicitly and checking its available artifacts and task status.

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

Your own site

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

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

When invoked 1,454 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.00016	$0.01454
Opus 5.5	$0.00006	$0.00582
Sonnet 5.5	$0.00003	$0.00291
Haiku 4.5	$0.00002	$0.00145

Measured 1mo ago against content hash 7709a72e1391, 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-verify 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-verify-change — 130 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-verify/SKILL.md · 169 lines

How it starts

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

source-command-opsx-verify

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

Command Template

Verify that an implementation matches the change artifacts (specs, tasks, design).

Input: Optionally specify a change name after /opsx:verify (e.g., /opsx:verify 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. Use the AskUserQuestion tool to let the user select.

Show changes that have implementation tasks (tasks artifact exists). Include the schema used for each change if available. Mark changes with incomplete tasks as "(In Progress)".

IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
Check status to understand the schema
```
openspec status --change "<name>" --json
```
Parse the JSON to understand:
- schemaName: The workflow being used (e.g., "spec-driven")
- Which artifacts exist for this change
Get the change directory and load artifacts
```
openspec instructions apply --change "<name>" --json
```
This returns the change directory and contextFiles (artifact ID -> array of concrete file paths). Read all available artifacts from contextFiles.
Initialize verification report structure

Create a report structure with three dimensions:
- Completeness: Track tasks and spec coverage
- Correctness: Track requirement implementation and scenario coverage
- Coherence: Track design adherence and pattern consistency
Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
Verify Completeness

Task Completion:
- If contextFiles.tasks exists, read every file path in it
- Parse checkboxes: - [ ] (incomplete) vs - [x] (complete)
- Count complete vs total tasks
- If incomplete tasks exist:
  - Add CRITICAL issue for each incomplete task
  - Recommendation: "Complete task: " or "Mark as done if already implemented"

Read the full file on GitHub · 169 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 · 169 lines · 16 tokens per session scan A 7709a72e1391

Subscribe to this mod's changes

source-command-opsx-verify is a skill published in the GitHub repository killin0415/memoir (5 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 1,454 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-verify-change, differing in 130 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.