A command for starting a software change with OPSX, an experimental workflow that records work as artifacts such as specifications and plans.

Use it to start a new change from a description or a kebab-case name, and to select the correct OpenSpec repository when needed.

It helps turn an idea or fix into a named, trackable change before implementation begins.

How HazelnutParadise/insyra configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to HazelnutParadise/insyra. 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/HazelnutParadise/insyra/main/.claude/commands/opsx/new.md

Clone the repo

git clone --depth 1 https://github.com/HazelnutParadise/insyra

Made for: Claude Code.

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/hazelnutparadise/insyra/new.svg)](https://agentmods.dev/commands/hazelnutparadise/insyra/new)

Your own site

<a href="https://agentmods.dev/commands/hazelnutparadise/insyra/new"><img src="https://agentmods.dev/badge/commands/hazelnutparadise/insyra/new.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 760 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.00018	$0.00760
Opus 5	$0.00009	$0.00380
Sonnet 5	$0.00004	$0.00152
Haiku 4.5	$0.00002	$0.00076

Measured 6d ago against content hash 4644616a3924, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

OPSX: New 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 6d 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: New — 10 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.

.claude/commands/opsx/new.md · 73 lines

What it actually says

Start a new change using the experimental artifact-driven approach.

Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.

Input: The argument after /opsx:new 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.
Determine the workflow schema

Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

Use a different schema only if the user mentions:
- A specific schema name → use --schema <name>
- "show workflows" or "what workflows" → run openspec schemas --json and let them choose
Otherwise: Omit --schema to use the default.
Create the change directory
```
openspec new change "<name>"
```
Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change in the planning home resolved by the CLI.
Show the artifact status
```
openspec status --change "<name>" --json
```
Use the returned planningHome, changeRoot, artifactPaths, and nextSteps instead of assuming repo-local paths.
Get instructions for the first artifact The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
```
openspec instructions <first-artifact-id> --change "<name>"
```
This outputs the template and context for creating the first artifact.
STOP and wait for user direction

Output

After completing the steps, summarize:

Change name and location
Schema/workflow being used and its artifact sequence
Current status (0/N artifacts complete)
The template for the first artifact
Prompt: "Ready to create the first artifact? Run /opsx:continue or just describe what this change is about and I'll draft it."

Guardrails

Do NOT create any artifacts yet - just show the instructions
Do NOT advance beyond showing the first artifact template
If the name is invalid (not kebab-case), ask for a valid name
If a change with that name already exists, suggest using /opsx:continue instead
Pass --schema if using a non-default workflow

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.

6d ago First seen · 73 lines · 18 tokens per session scan A 4644616a3924

Subscribe to this mod's changes

OPSX: New is a command published in the GitHub repository HazelnutParadise/insyra (56 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 760 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: New, differing in 10 lines, and is treated as a copy.

Go Productivity analysis artifacts data-science experimental go-echarts parallel stats workflow

insyra: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

OPSX: Apply

OPSX: Apply

OPSX: Propose

OPSX: Continue

OPSX: Propose

OPSX: Apply