analyze-change-impact

analyze-change-impact is a command for GitHub Copilot from ChenyCHENYU/wl-skills-design. It costs 18 tokens per session (184 once invoked), scanned A, original, Apache-2.0.

A read-only command that examines how a design change affects six areas: requirements, terminology, database, API, prototype, and review. It produces a patch plan, meaning an ordered list of follow-up changes.

In plain words
What is it for?
It is for finding affected design areas, assigning priority and dependencies to follow-up tasks, defining completion conditions, and running checks.
Why use it?
It shows what a change may break or require across related design documents before anyone edits them.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: agent in frontmatter.

Good fit It is for finding affected design areas, assigning priority and dependencies to follow-up tasks, defining completion conditions, and running checks.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/chenychenyu/wl-skills-design/analyze-change-impact
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.

Clone the repo
git clone --depth 1 https://github.com/ChenyCHENYU/wl-skills-design

Made for: GitHub Copilot.

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.

agentmods badge for analyze-change-impact

README.md
[![agentmods](https://agentmods.dev/badge/commands/chenychenyu/wl-skills-design/analyze-change-impact/github.svg)](https://agentmods.dev/commands/chenychenyu/wl-skills-design/analyze-change-impact)
Your own site
<a href="https://agentmods.dev/commands/chenychenyu/wl-skills-design/analyze-change-impact"><img src="https://agentmods.dev/badge/commands/chenychenyu/wl-skills-design/analyze-change-impact/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.

agentmods 80×15 button for analyze-change-impact

Your own site · 80×15
<a href="https://agentmods.dev/commands/chenychenyu/wl-skills-design/analyze-change-impact"><img src="https://agentmods.dev/badge/commands/chenychenyu/wl-skills-design/analyze-change-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 184 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00184
Opus 5.5 $0.00007 $0.00074
Sonnet 5.5 $0.00004 $0.00037
Haiku 4.5 $0.00002 $0.00018

Measured 11d ago against content hash 6f51764311b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze-change-impact 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 11d 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.

files/.github/prompts/analyze-change-impact.prompt.md · 14 lines

What it actually says

分析变更影响

变更:${input:change:请提供变更对象、动作和目标描述}

  1. 读取 变更影响 Skill 和 变更影响标准。
  2. 对 spec、glossary、DB、API、prototype、review 六个域逐一判断影响并给出证据。
  3. 输出 P0/P1/P2 补丁任务、依赖顺序、完成条件和复验入口。
  4. 执行 CI-A/B/C/X 共 20 项检查。默认只读;只在用户要求保存报告时写入 docs/change-impact/。
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. 11d ago First seen · 14 lines · 18 tokens per session scan A 6f51764311b0

Subscribe to this mod's changes

analyze-change-impact is a command published in the GitHub repository ChenyCHENYU/wl-skills-design (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 184 once invoked, about $0.0001 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-10-06.