agentmods.dev

OPSX: New

A command that starts a new OpenSpec change, where a change is a proposed feature or fix described through planning documents. It creates the change's folder and asks for details when no description is provided.

In plain words
What is it for?
Use it to start documenting a feature or bug fix, derive a kebab-case change name from a description, choose an OpenSpec workflow when needed, and create the initial change structure.
Why use it?
It gives a new piece of work a consistent name and planning structure before implementation begins. The workflow can use a requested schema, or the default one when no schema is specified.

Command for Claude Code

5 18d ago A scan 18 tokens copy · 100% Apache-2.0
View the source file justinjdev/fellowship
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/justinjdev/fellowship/new
Clone the repo
git clone --depth 1 https://github.com/justinjdev/fellowship

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 610 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% 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 $0.00018 $0.00610
Opus 5 $0.00009 $0.00305
Sonnet 5 $0.00004 $0.00122
Haiku 4.5 $0.00002 $0.00061

Measured yesterday against content hash 6cbc55fc0603, 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

100% identical to OPSX: New — 0 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 · 70 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

  1. 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.

  2. 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.

  3. 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.

  4. Show the artifact status

    openspec status --change "<name>"

    This shows which artifacts need to be created and which are ready (dependencies satisfied).

  5. 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.

  6. 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.

  1. yesterday First seen · 70 lines · 18 tokens per session scan A 6cbc55fc0603

Subscribe to this mod's changes

OPSX: New is a command published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 18d ago), licensed Apache-2.0. It adds 18 tokens to every session and 610 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to OPSX: New, differing in 0 lines, and is treated as a copy.

Data and AIDebuggingMulti-AgentPlanningai-agentsartifactsclaude-codeclaude-code-plugindeveloper-toolsexperimentalprompt-engineeringworkflow
Related

Other commands, from other repositories

OPSX: Apply

Implement tasks from an OpenSpec change (Experimental).

Chorus-AIDLC/Chorus · 15 tokens

OPSX: Propose

Propose a new change - create it and generate all artifacts in one step.

Chorus-AIDLC/Chorus · 21 tokens

OPSX: Apply

Implement tasks from an OpenSpec change (Experimental).

HsienW/chat-gun-react-agent · 15 tokens

OPSX: Continue

Continue working on a change - create the next artifact (Experimental).

HsienW/chat-gun-react-agent · 18 tokens

OPSX: Propose

Propose a new change - create it and generate all artifacts in one step.

HsienW/chat-gun-react-agent · 21 tokens

OPSX: New

Start a new change using the experimental artifact workflow (OPSX).

HsienW/chat-gun-react-agent · 18 tokens