A command that starts a software change through an experimental workflow based on written work artifacts.

Use it to open a new change, choose its workflow, and create the initial change structure.

It gives a new feature or fix a defined starting point and asks for clarification when the request is unclear.

How mendix/web-widgets configures Claude Code

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/mendix/web-widgets

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/mendix/web-widgets/new/github.svg)](https://agentmods.dev/commands/mendix/web-widgets/new)

Your own site

<a href="https://agentmods.dev/commands/mendix/web-widgets/new"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/new/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/mendix/web-widgets/new"><img src="https://agentmods.dev/badge/commands/mendix/web-widgets/new.svg" alt="Reviewed on agentmods" width="80" 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 717 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.00018	$0.00717
Opus 5.5	$0.00007	$0.00287
Sonnet 5.5	$0.00004	$0.00143
Haiku 4.5	$0.00002	$0.00072

Measured 1mo ago against content hash 9c4ef2715bf6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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 — 61 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 · 85 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 (inside the target package)

Specs/changes are PER-PACKAGE. First determine which package this change belongs to (ask the user if unclear), then cd into it before running openspec. NEVER create changes at the monorepo root — a guardrail hook blocks it.
```
cd packages/<type>/<name-web> && openspec new change "<name>"
```
Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at packages/<type>/<name-web>/openspec/changes/<name>/ with the selected schema. If the package has no openspec/ yet, run openspec init inside the package first.
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.

1mo ago First seen · 85 lines · 18 tokens per session scan A 9c4ef2715bf6

Subscribe to this mod's changes

OPSX: New is a command published in the GitHub repository mendix/web-widgets (40 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 717 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to OPSX: New, differing in 61 lines, and is treated as a copy.

Planning Project management artifacts experimental low-code mendix web-widgets workflow

web-widgets: 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: New

OPSX: Continue

OPSX: Propose

OPSX: Apply

OPSX: Fast Forward

OPSX: Continue