What is /opsx-archive?

A command for archiving a completed change in an experimental OpenSpec workflow. OpenSpec is a tool that tracks a change through required planning documents called artifacts.

Use it after finishing a change to list available changes, check their completion status, confirm any warnings, and archive the selected one.

It prevents the wrong change from being archived and warns when its required documents are incomplete. When no change is named, it asks the user to choose instead of guessing.

How ly1836/spring-ai-rag-demo configures Claude Code and Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to ly1836/spring-ai-rag-demo. 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/ly1836/spring-ai-rag-demo/main/.cursor/commands/opsx-archive.md

Clone the repo

git clone --depth 1 https://github.com/ly1836/spring-ai-rag-demo

Made for: Claude Code, Cursor.

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/commands/ly1836/spring-ai-rag-demo/opsx-archive/github.svg)](https://agentmods.dev/commands/ly1836/spring-ai-rag-demo/opsx-archive)

Your own site

<a href="https://agentmods.dev/commands/ly1836/spring-ai-rag-demo/opsx-archive"><img src="https://agentmods.dev/badge/commands/ly1836/spring-ai-rag-demo/opsx-archive/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/commands/ly1836/spring-ai-rag-demo/opsx-archive"><img src="https://agentmods.dev/badge/commands/ly1836/spring-ai-rag-demo/opsx-archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,380 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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.01380
Opus 5	$0.00007	$0.00690
Sonnet 5	$0.00003	$0.00276
Haiku 4.5	$0.00001	$0.00138

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

Security

Grade A, and why

/opsx-archive 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 OPSX: Archive — 49 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.

.cursor/commands/opsx-archive.md · 178 lines

How it starts

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

Archive a completed change in the experimental workflow.

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

Steps

项目确认（必须首先执行）

本项目是单模块 Spring Boot 应用，OpenSpec 统一在仓库根目录管理，change 名称不使用模块前缀。 所有 CLI 命令在项目根目录执行。 如需列出 changes，直接在根目录执行 openspec list --json。
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 only active changes (not already archived). Include the schema used for each change if available.

IMPORTANT: Do NOT guess or auto-select a change. Always let the user choose.
Check artifact completion status

Run openspec status --change "<name>" --json to check artifact completion.

Parse the JSON to understand:
- schemaName: The workflow being used
- artifacts: List of artifacts with their status (done or other)
If any artifacts are not done:
- Display warning listing incomplete artifacts
- Prompt user for confirmation to continue
- Proceed if user confirms
Check task completion status

Read the tasks file (typically tasks.md) to check for incomplete tasks.

Count tasks marked with - [ ] (incomplete) vs - [x] (complete).

If incomplete tasks found:
- Display warning showing count of incomplete tasks
- Prompt user for confirmation to continue
- Proceed if user confirms
If no tasks file exists: Proceed without task-related warning.
Assess delta spec sync state

Check for delta specs at openspec/changes/<name>/specs/. If none exist, proceed without sync prompt.

If delta specs exist:
- Compare each delta spec with its corresponding main spec at openspec/specs/<capability>/spec.md
- Determine what changes would be applied (adds, modifications, removals, renames)
- Show a combined summary before prompting
Prompt options:
- If changes needed: "Sync now (recommended)", "Archive without syncing"
- If already synced: "Archive now", "Sync anyway", "Cancel"
If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change ''. Delta spec analysis: "). Proceed to archive regardless of choice.
Perform the archive

Create the archive directory if it doesn't exist:
```
mkdir -p openspec/changes/archive
```
Generate target name using current date: YYYY-MM-DD-<change-name>

Check if target already exists:
- If yes: Fail with error, suggest renaming existing archive or using different date
- If no: Move the change directory to archive
```
mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
```
Normalize generated main specs

If archiving created or updated openspec/specs/<capability>/spec.md, read the generated main spec and immediately normalize any tool-generated English shell content before declaring success.

Must fix cases like:
- # <capability> Specification
- TBD - created by archiving change ...
- Update Purpose after archive.
Normalization rules:
- Keep OpenSpec-required structure keywords such as ## Purpose, ## Requirements
- Convert the title to Chinese, e.g. # <capability> 规格
- Replace placeholder Purpose text with a formal Chinese description based on the archived delta spec
Display summary

Show archive completion summary including:
- Change name
- Schema that was used
- Archive location
- Spec sync status (synced / sync skipped / no delta specs)
- Note about any warnings (incomplete artifacts/tasks)

Output On Success

## Archive Complete

**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** ✓ Synced to main specs

All artifacts complete. All tasks complete.

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

10d ago First seen · 178 lines · 14 tokens per session scan A 0623e2b98751

Subscribe to this mod's changes

/opsx-archive is a command published in the GitHub repository ly1836/spring-ai-rag-demo (86 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,380 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 OPSX: Archive, differing in 49 lines, and is treated as a copy.

ai-agents deepseek docker echarts erp gemini workflow

context

A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.

fengshao1227/ccg-workflow · 23 tokens

clean-branches

A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.

fengshao1227/ccg-workflow · 23 tokens

init

A project-initialization command that scans a codebase and creates or updates CLAUDE.md files. These files give AI coding tools project and module instructions, and the command also creates navigation diagrams.

fengshao1227/ccg-workflow · 20 tokens

rollback

An interactive Git command for moving a branch back to an earlier commit, tag, or saved reference. It supports reset, which changes branch history, and revert, which adds new commits that undo earlier ones.

fengshao1227/ccg-workflow · 22 tokens

spec-impl

An implementation command that follows an approved specification and task checklist, uses multiple analysis models, and archives the completed work. It keeps changes within the defined scope and requires external suggestions to be reviewed before use.

fengshao1227/ccg-workflow · 12 tokens

spec-research

A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.

fengshao1227/ccg-workflow · 16 tokens

spring-ai-rag-demo: Command for Claude Code