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.
git clone --depth 1 https://github.com/Aimeerrhythm/enterprise-change-workflowWrote 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/commands/aimeerrhythm/enterprise-change-workflow/ecw-upgrade)<a href="https://agentmods.dev/commands/aimeerrhythm/enterprise-change-workflow/ecw-upgrade"><img src="https://agentmods.dev/badge/commands/aimeerrhythm/enterprise-change-workflow/ecw-upgrade/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.
<a href="https://agentmods.dev/commands/aimeerrhythm/enterprise-change-workflow/ecw-upgrade"><img src="https://agentmods.dev/badge/commands/aimeerrhythm/enterprise-change-workflow/ecw-upgrade.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.01991 |
| Opus 5 | $0.00012 | $0.00996 |
| Sonnet 5 | $0.00005 | $0.00398 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade B, and why
ecw-upgrade scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Do **not** modify global `~/.claude/settings.json`. How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ECW Upgrade — Project Configuration Sync
You are executing the /ecw-upgrade command. Your task is to compare the project's ECW configuration against current plugin templates, fix everything you can, and auto-validate the result.
Important: This command belongs to the enterprise-change-workflow plugin. All templates are in the plugin's templates/ directory. Read them using the Read tool from the plugin installation path (i.e., templates/ under the parent directory containing this commands/ folder).
Step 0: Prerequisite Check
Check if .claude/ecw/ecw.yml exists. If not:
ECW not initialized. Please run /ecw-init first.
Then stop.
Step 1: Run All Idempotent Checks
Read each project config file and compare against the current plugin template. For each check, determine status: ok (matches template structure) or needs-fix (outdated/missing/malformed).
Check A: ecw.yml Structure Sync
Check: Read project .claude/ecw/ecw.yml and plugin templates/ecw.yml. Compare:
- Missing sections — If template has a top-level key (e.g.,
tdd:,paths:,auto_flow:) that project file lacks, inject the section from template with default values. - Missing fields within sections — If template has fields inside a section (e.g.,
paths.knowledge_root,tdd.enabled) that project file lacks, add them with template defaults. - Unknown fields (info only) — If project file has top-level keys NOT in the template, report them but do NOT remove. User may have intentional custom extensions.
- Preserve user values — Never overwrite fields that exist in both template and project; only add missing ones.
For each fix, use Edit tool to surgically add/remove. Do not rewrite the entire file.
Check B: TDD Enabled for Java Projects
Check: Run ls pom.xml 2>/dev/null in project root to detect Java project.
pom.xmlnot found → skip (non-Java project, TDD auto-enable not applicable)pom.xmlfound → Read project.claude/ecw/ecw.yml, checktdd.enabled:true→ okfalseor field missing → needs-fix: Settdd.enabled: trueusing Edit tool
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.
- 8d ago First seen · 188 lines · 24 tokens per session scan B 6177c6d7ec95
ecw-upgrade is a command published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 1,991 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
check
Verify an implementation against the CCF spec — conformance, coding conventions, SOLID/OOP, and BE↔FE cross-check. Read-only review.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
init
Install the formatters this repository needs, with every command visible before it runs.
sonarqube
Analyze SonarCloud quality issues for a specific PR.