A command that starts a software change using OPSX, an experimental workflow based on planning and saved work artifacts.

Use it to start a new coding task, derive a change name from a description, choose a workflow schema when needed, and create the initial change directory.

It gives a new feature or fix a named, scaffolded workspace and makes the intended workflow explicit before implementation begins.

OPSX: New — Command by Nxtsoft

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 commands/nxtsoft/cgraph/new

Clone the repo

git clone --depth 1 https://github.com/Nxtsoft/CGraph

Made for: Claude Code.

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 631 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 94% 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	$0.00018	$0.00631
Opus 5	$0.00009	$0.00316
Sonnet 5	$0.00004	$0.00126
Haiku 4.5	$0.00002	$0.00063

Measured yesterday against content hash 74faa7faca15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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

94% identical to OPSX: New — 1 line 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 · 71 lines

What it actually says

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

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 at openspec/changes/<name>/ with the selected schema.
Show the artifact status
```
openspec status --change "<name>"
```
This shows which artifacts need to be created and which are ready (dependencies satisfied).
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.

yesterday First seen · 71 lines · 18 tokens per session scan A 74faa7faca15

Subscribe to this mod's changes

OPSX: New is a command published in the GitHub repository Nxtsoft/CGraph (2 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 631 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to OPSX: New, differing in 1 line, and is treated as a copy.

Planning Productivity artifacts experimental workflow

OPSX: New

Getting it into your agent

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: Propose

OPSX: Continue

OPSX: New

OPSX: Propose

OPSX: Apply