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.
/plugin marketplace add Aimeerrhythm/enterprise-change-workflow/plugin install ecwWrote 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.
[](https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/workspace)<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/workspace"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/workspace.svg" alt="Measured on agentmods" height="20"></a>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.00039 | $0.02318 |
| Opus 5 | $0.00019 | $0.01159 |
| Sonnet 5 | $0.00008 | $0.00464 |
| Haiku 4.5 | $0.00004 | $0.00232 |
Grade A, and why
workspace 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace — Multi-Repo Cross-Service Development
Manage cross-service workspaces and coordinate multi-session parallel development. Each service runs its own independent ECW flow; this Skill handles workspace lifecycle and master coordination.
Output language: Read output_language for the workspace session:
- Try any ECW-ready service's
.claude/ecw/ecw.yml→project.output_language - Fallback:
workspace.yml→output_language - Fallback: detect from user's input language
All coordinator-written files must use this language for headings, labels, and descriptive text. Pass output_language explicitly in every dispatched child session prompt.
File encoding: All files must use native UTF-8 characters. Never use Unicode escape sequences.
Core principle: Workspace = infrastructure (git worktree), Coordinator = orchestration (Phase-Gate flow), per-service ECW = execution (unchanged). Three layers, orthogonal.
Announce at start: "Using ecw:workspace to [create workspace / coordinate cross-service development / ...]."
When to Use
Use when:
- User needs to develop across 2+ independent git repositories simultaneously
- Cross-service changes with interface dependencies (Dubbo, MQ)
- Need coordinated implementation with contract alignment
Don't use when:
- Single-repo multi-module change (use standard ECW flow)
- Services are in a monorepo (use ecw:domain-collab instead)
- Pure read-only analysis (no implementation needed)
Sub-commands
| Sub-command | Usage | Description |
|---|---|---|
create |
/ecw:workspace create <services...> [--name] [--branch] |
Create workspace + auto-enter + start run |
run |
/ecw:workspace run "<requirement>" |
6-Phase coordinator flow |
status |
/ecw:workspace status |
All services' git + session status |
push |
/ecw:workspace push |
Batch push with confirmation |
destroy |
/ecw:workspace destroy |
Clean up worktrees + directory |
One-command flow: create captures the requirement, creates workspace, opens new session, starts run automatically. Manual only — not auto-triggered by risk-classifier.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 219 lines · 39 tokens per session scan A 91aa02b1f887
workspace is a skill published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 2,318 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
pr-review
PR self-review — review changes, produce checklist, update rules.
check-pr
Read-only inspection of a single GitHub PR lifecycle — checks CI, review threads, description sync, and mergeability, and returns PASS or FAIL with per-gate findings. Never invokes the merge button. Use when verifying a PR is ready to merge, polling lifecycle progress, checking mergeability, or babysitting a GitHub PR…
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…