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.
npx skills add Aimeerrhythm/enterprise-change-workflow --skill biz-impact-analysisgit 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/skills/aimeerrhythm/enterprise-change-workflow/biz-impact-analysis)<a href="https://agentmods.dev/skills/aimeerrhythm/enterprise-change-workflow/biz-impact-analysis"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/biz-impact-analysis/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/skills/aimeerrhythm/enterprise-change-workflow/biz-impact-analysis"><img src="https://agentmods.dev/badge/skills/aimeerrhythm/enterprise-change-workflow/biz-impact-analysis.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.00036 | $0.01627 |
| Opus 5 | $0.00018 | $0.00813 |
| Sonnet 5 | $0.00007 | $0.00325 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
biz-impact-analysis 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 10d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Impact Analysis
After code changes are complete, dispatch the biz-impact-analysis agent to analyze the impact of changes on business processes.
Announce at start: "Using ecw:biz-impact-analysis to assess business impact of code changes."
Output language: Read ecw.yml → project.output_language. Pass to dispatched agent prompt. Report headings and labels follow this language.
Flow
- Determine Diff Range — Resolution priority:
- With explicit args (e.g.
git diff abc123...HEAD): usegit diff {args}directly. - No args + ECW session-state: read
baseline_commitfrom.claude/ecw/session-data/{workflow-id}/session-state.jsonand usegit diff {baseline_commit}...HEAD. This bounds the analysis to the current workflow. - No args + no session-state: fall back to
git diff main...HEAD(ormaster...HEADin legacy repos).bash-preflightwill rewrite this to{baseline}...HEADwhen a baseline is available; if not, expect noise from unrelated historical commits.
- With explicit args (e.g.
- Coordinator Preprocessing — Execute before Agent dispatch:
- Run
git diff --stat {diff_range}to get change statistics - Run
git diff --name-only {diff_range}to get file list - Read
path-mappings.md, map file list to domains - Fill above results into Agent prompt, replacing full diff
- Run
Knowledge file robustness: If
path-mappings.mdis missing, pass the raw file list to the Agent without domain mapping. The Agent will use path-based heuristic grouping and note[Warning: path mappings not found, domain identification is heuristic]in the report.
- Dispatch biz-impact-analysis agent — Read
./prompts/agent-prompt-template.mdfor the dispatch prompt structure and argument parsing rules. Model:opus(default frommodels.defaults.analysis; configurable via ecw.yml). Timeout: 300s. Budget cap: single agent, no retry loop — one attempt plus one retry on format failure only. Pass in preprocessed results, await impact analysis report - Return value validation: Verify the agent's report contains required sections ("Analysis Coverage", "Change Summary", "Direct Impact"). If the report is missing critical sections:
- Log to Ledger:
[FAILED: biz-impact-analysis, reason: incomplete report] - Retry once with the same model
- If retry also fails: output the partial report as-is with
[degraded: incomplete analysis]header, and warn user that manual impact review may be needed
- Log to Ledger:
- Auto-backfill knowledge base — If the agent's report contains "Unregistered Cross-Domain Calls", execute the knowledge backfill procedure (see Knowledge Auto-Backfill below)
- Present analysis report — Write the full report to
session-data/{workflow-id}/biz-impact-report.md(read theworkflow_idfield fromsession-state.json). Then output the agent's formatted report directly; append backfill summary if any calls were added - Mark Task complete — Mark the biz-impact-analysis Task as complete via TaskUpdate
What ships with it
2 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.
- 10d ago First seen · 102 lines · 36 tokens per session scan A f591ea0d4b55
biz-impact-analysis is a skill published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,627 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
g-review
Run the review gate on the current branch diff. Runs the test suite, captures the diff, and dispatches code-lead, which verifies done conditions and reviews the diff itself. Issues MERGE READY or HOLD.
g-refactor
Guided refactor workflow — identify target, pre-analyse, spec, approve, execute, review. Accepts a scope path, an audit milestone file, or runs interactively. Safe-by-default: checks test coverage before execution and runs the full review gate after.
g-audit
Full-codebase or targeted code quality audit. Detects SOLID violations, code smells, architectural drift, dead code, and test coverage gaps. Targeted scope produces an inline report. Whole-codebase scope produces a prioritised roadmap milestone.
g-blast-radius
Analyse the blast radius of a planned change. Inputs a file path, feature name, or list of paths from a plan. Outputs the set of dependent files (forward and reverse references), a per-file volatility score (commit frequency proxy), and a total blast-radius rating (low / moderate / wide). Read-only.
cross-verify
A cross-checking skill that reviews decisions, designs, documents, and implementations from four viewpoints.
decompose
Break a large goal into 3–8 sequenced tasks, each one /eng → /tdd cycle. Writes to specs/{slug}.todos.md when a spec exists, root TODOS.md otherwise. /decompose — decompose a feature or goal /decompose re-entry — resume where you left off (auto-detected).