validate-change-impact

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

A read-only checker for a change-impact report, which explains what parts of a design or system may be affected by a change. It checks coverage, evidence, task dependencies, and the order of rechecks.

In plain words
What is it for?
Use it to review a CHANGE_IMPACT report, list failed and pending rules with locations, and identify actionable follow-up work.
Why use it?
It reveals unsupported conclusions, missing affected areas, and tasks that cannot be carried out as written. It does not change the report or the related design files unless you explicitly request a repair.

Command for GitHub Copilot

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

Good fit Use it to review a CHANGE_IMPACT report, list failed and pending rules with locations, and identify actionable follow-up work.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/chenychenyu/wl-skills-design/validate-change-impact"><img src="https://agentmods.dev/badge/commands/chenychenyu/wl-skills-design/validate-change-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 176 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.00020 $0.00176
Opus 5.5 $0.00008 $0.00070
Sonnet 5.5 $0.00004 $0.00035
Haiku 4.5 $0.00002 $0.00018

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

Security

Grade A, and why

validate-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/validate-change-impact.prompt.md · 14 lines

What it actually says

验证变更影响报告

目标:${input:file:请输入 CHANGE_IMPACT 报告路径}

  1. 读取 变更影响 Skill 和 变更影响标准。
  2. 执行 CI-A/B/C/X 共 20 项检查,确认六域判断、证据、任务依赖和完成条件。
  3. 输出规则 ID、位置、失败、Pending 和建议,不修改报告或设计产物。
  4. 用户明确要求修复报告后,才可展示差异、修改报告并复验;不得借此批量修改设计文件。
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 · 20 tokens per session scan A 8a751504fcf7

Subscribe to this mod's changes

validate-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 20 tokens to every session and 176 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.