agentmods.dev

source-command-opsx-apply

source-command-opsx-apply is a skill for Claude Code, Codex from zhe-qi/clhoria-template. It costs 18 tokens per session (1,089 once invoked), scanned A, a copy of openspec-apply-change, MIT.

A workflow command for implementing the tasks described by an OpenSpec change. OpenSpec is a structured process for planning and tracking software changes.

In plain words
What is it for?
Use it to select an OpenSpec change, inspect its status and instructions, and carry out the listed implementation tasks.
Why use it?
It connects a documented change plan to the implementation steps and checks which change and workflow format should be used first.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool; installed under .agents/ (shared by several agents).

not rated 191repo 1mo ago A scan 18 tokens copy · 83% MIT

Good fit Use it to select an OpenSpec change, inspect its status and instructions, and carry out the listed implementation tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zhe-qi/clhoria-template/source-command-opsx-apply
View source ↗ zhe-qi/clhoria-template
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 zhe-qi/clhoria-template --skill source-command-opsx-apply
Clone the repo
git clone --depth 1 https://github.com/zhe-qi/clhoria-template

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-apply

README.md
[![agentmods](https://agentmods.dev/badge/skills/zhe-qi/clhoria-template/source-command-opsx-apply/github.svg)](https://agentmods.dev/skills/zhe-qi/clhoria-template/source-command-opsx-apply)
Your own site
<a href="https://agentmods.dev/skills/zhe-qi/clhoria-template/source-command-opsx-apply"><img src="https://agentmods.dev/badge/skills/zhe-qi/clhoria-template/source-command-opsx-apply/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 source-command-opsx-apply

Your own site · 80×15
<a href="https://agentmods.dev/skills/zhe-qi/clhoria-template/source-command-opsx-apply"><img src="https://agentmods.dev/badge/skills/zhe-qi/clhoria-template/source-command-opsx-apply.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,089 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 83% 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.00018 $0.01089
Opus 5 $0.00009 $0.00544
Sonnet 5 $0.00004 $0.00218
Haiku 4.5 $0.00002 $0.00109

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

Security

Grade A, and why

source-command-opsx-apply 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 10d 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

83% identical to openspec-apply-change — 26 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-apply/SKILL.md · 157 lines

How it starts

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

source-command-opsx-apply

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

Command Template

Implement tasks from an OpenSpec change.

Input: Optionally specify a change name (e.g., /opsx:apply 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. Select the change

    If a name is provided, use it. Otherwise:

    • Infer from conversation context if the user mentioned a change
    • Auto-select if only one active change exists
    • If ambiguous, run openspec list --json to get available changes and use the AskUserQuestion tool to let the user select

    Always announce: "Using change: " and how to override (e.g., /opsx:apply <other>).

  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 artifact contains the tasks (typically "tasks" for spec-driven, check status for others)

  3. Get apply instructions

    openspec instructions apply --change "<name>" --json

    This returns:

    • Context file paths (varies by schema)
    • Progress (total, complete, remaining)
    • Task list with status
    • Dynamic instruction based on current state

    Handle states:

    • If state: "blocked" (missing artifacts): show message, suggest using /opsx:continue
    • If state: "all_done": congratulate, suggest archive
    • Otherwise: proceed to implementation

  4. Read context files

    Read the files listed in contextFiles from the apply instructions output. The files depend on the schema being used:

    • spec-driven: proposal, specs, design, tasks
    • Other schemas: follow the contextFiles from CLI output

  5. Show current progress

    Display:

    • Schema being used
    • Progress: "N/M tasks complete"
    • Remaining tasks overview
    • Dynamic instruction from CLI

Read the full file on GitHub · 157 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. 10d ago First seen · 157 lines · 18 tokens per session scan A 305057c863fa

Subscribe to this mod's changes

source-command-opsx-apply is a skill published in the GitHub repository zhe-qi/clhoria-template (191 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 1,089 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to openspec-apply-change, differing in 26 lines, and is treated as a copy.

Planningbackend-boilerplatebackend-templatehono-boilerplate
Related

Other skills, from other repositories

add-vertical

Use this skill when adding a new feature vertical to this template — a domain aggregate with its port, repository, application service, DTOs, endpoint, and tests. Trigger it for requests like "add an endpoint", "add a new entity", "build the X feature", or "wire up a new service".

LamantinAI/mayak · 67 tokens

initialize-project

Use this skill when asked to initialize, bootstrap, or set up a repository created from the Mayak template so local development is ready. Trigger it for requests like "initialize the project", "bootstrap this repo", "set up the project locally", or "prepare the repo for work".

LamantinAI/mayak · 60 tokens

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens