A workspace creation command for starting a named working area inside an onboarded repository. Workspaces are separate folders for tasks such as an epic, an experiment, or a pull request.

Use it to create epic-, spike-, or pull-request workspaces for a selected repository, with an optional purpose and owner.

It sets up the workspace with a valid name and records its purpose and owner, so task work stays organized within the repository collection.

new — Command for Claude Code by mdsakalu/agent-plugins

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add mdsakalu/agent-plugins

Claude Code

/plugin install workspace

Made for: Claude Code.

Or install workspace, the plugin that ships this one along with the rest of its 13 commands, 3 hooks.

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/mdsakalu/agent-plugins/new/github.svg)](https://agentmods.dev/commands/mdsakalu/agent-plugins/new)

Your own site

<a href="https://agentmods.dev/commands/mdsakalu/agent-plugins/new"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/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/mdsakalu/agent-plugins/new"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/new.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 708 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 original No closer match found 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.00009	$0.00708
Opus 5.5	$0.00004	$0.00283
Sonnet 5.5	$0.00002	$0.00142
Haiku 4.5	$0.00001	$0.00071

Measured 1mo ago against content hash db3748b71bc9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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.

workspace/commands/new.md · 45 lines

How it starts

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

Create a new workspace for any onboarded repository.

Resolve the metarepo path by reading ~/.claude/workspace-config.json and expanding ~ to $HOME.

The user's request: $ARGUMENTS

Steps

Read ~/.claude/workspace-config.json to get the metarepo path. Expand ~ to $HOME.
Parse the user's request for:
- Repo name — which onboarded repository (e.g., my-repo)
- Workspace name — must match: epic-<kebab>, spike-<kebab>, or pr-<number>
- Purpose (optional) — short description of the workspace's goal
- Owner (optional) — defaults to the user
Discover available repos by scanning <metarepo>/repos/ for directories with .repo.json.
If the repo is ambiguous or missing:
- List available repos and ask the user via AskUserQuestion
- If no repos are onboarded, suggest /workspace:add-repo
If the repo is not onboarded, suggest: /workspace:add-repo <org/repo>
Validate the workspace name (must match epic-*, spike-*, or pr-* pattern).

Run the creation script:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/workspaces/new-workspace.sh <repo> <name> --type <type> --purpose "<purpose>" --owner "<owner>"

Show the output and the workspace path: <metarepo>/repos/<repo>/<name>/
Ask the user what to do next using AskUserQuestion:
- Stay here — don't cd, remain in the current directory
- cd (keep context) — invoke /workspace:cd <repo>/<name> to switch while preserving the current conversation
- cd (fresh session) — invoke /workspace:cd <repo>/<name> to switch with a fresh Claude session (zmx respawn) If the user picks "cd (keep context)" or "cd (fresh session)", invoke the workspace:cd skill with the appropriate workspace path. For "cd (fresh session)", pass --fresh as an additional argument.

Important

Always resolve metarepo from ~/.claude/workspace-config.json, never hardcode paths.
Workspace directories live under <metarepo>/repos/<repo>/<name>/.
Notes live under <metarepo>/notes/<repo>/<name>/ (git-tracked).
The script creates JJ workspace, workspace.json, README.md, and symlinks.
For pr-* workspaces, the script auto-fetches PR branch info via gh pr view.
Infer type from name prefix: epic-* → epic, spike-* → spike, pr-* → pr.

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

1mo ago First seen · 45 lines · 9 tokens per session scan A db3748b71bc9

Subscribe to this mod's changes

new is a command published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 708 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

dispatcher

Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…

Kanevry/session-orchestrator · 185 tokens

workpm

A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.

Dannykkh/skill-olympus · 31 tokens