agentmods.dev

source-command-opsx-verify

source-command-opsx-verify is a skill for Claude Code, Codex from killin0415/memoir. It costs 16 tokens per session (1,454 once invoked), scanned A, a copy of openspec-verify-change, MIT.

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.

In plain words
What is it for?
Use it to choose an OpenSpec change, inspect its workflow status and artifacts, and verify that the completed implementation matches the documented requirements.
Why use it?
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.

Skill for Claude CodeCodex

not rated 5 2mo ago A scan 16 tokens copy · 81% MIT
View the source file killin0415/memoir
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.

agentmods
npx agentmods add skills/killin0415/memoir/source-command-opsx-verify
Any agent
npx skills add killin0415/memoir --skill source-command-opsx-verify
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.

agentmods badge for source-command-opsx-verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/killin0415/memoir/source-command-opsx-verify.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.svg" alt="Measured on agentmods" 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. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.01454
Opus 5 $0.00008 $0.00727
Sonnet 5 $0.00003 $0.00291
Haiku 4.5 $0.00002 $0.00145

Measured 3d ago against content hash 7709a72e1391, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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 — 38 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

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

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

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

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

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

  1. 3d 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 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,454 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to openspec-verify-change, differing in 38 lines, and is treated as a copy.

Planning
Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens