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 rockyflux/yq-workflow --skill verify-changegit clone --depth 1 https://github.com/rockyflux/yq-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/rockyflux/yq-workflow/verify-change)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/verify-change"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/verify-change/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/rockyflux/yq-workflow/verify-change"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/verify-change.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.00065 | $0.01057 |
| Opus 5 | $0.00032 | $0.00528 |
| Sonnet 5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
verify-change 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 5d 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.
This is a copy
100% identical to verify-change — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
⚖ 校验关卡 · 变更校验
核心原则
变更 = 代码改动 + 文档更新 + 理由记录
无理由的变更是隐患，无记录的变更是灾难
每一次变更都是历史，每一个决策都要留痕
自动分析
运行变更分析脚本（跨平台）：
# 在 skill 目录下运行
node scripts/change_analyzer.js # 分析工作区变更（默认）
node scripts/change_analyzer.js --mode staged # 分析暂存区变更
node scripts/change_analyzer.js --mode committed # 分析已提交变更
node scripts/change_analyzer.js -v # 详细模式
node scripts/change_analyzer.js --json # JSON 输出
检测能力
自动检测项
| 检测项 | 说明 |
|---|---|
| 文件分类 | 自动识别代码/文档/测试/配置文件 |
| 模块识别 | 识别受影响的模块 |
| 文档同步 | 检测代码变更是否同步更新文档 |
| 测试覆盖 | 检测代码变更是否有对应测试 |
| 影响评估 | 评估变更规模和影响范围 |
触发警告的情况
- ⚠️ 代码变更 > 50 行但 DESIGN.md 未更新
- ⚠️ 代码变更 > 30 行但无测试更新
- ⚠️ 新增文件但 README.md 未更新
- ⚠️ 配置文件变更未记录
- ℹ️ 删除文件需确认引用已清理
变更前置检查
在修改任何模块前，必须：
- 读取 README.md — 理解模块定位
- 读取 DESIGN.md — 理解现有决策
- 评估影响范围 — 此变更影响哪些部分
- 确认变更理由 — 为什么要改
变更后置检查
代码修改完成后，必须：
README.md 更新检查
- 模块职责是否变化 → 更新职责描述
- 依赖关系是否变化 → 更新依赖说明
- 使用方式是否变化 → 更新示例代码
DESIGN.md 更新检查
- 新增设计决策 → 记录决策及理由
- 修改现有设计 → 记录变更及原因
- 引入新限制 → 更新已知限制
- 添加变更记录 → 更新变更历史
变更记录格式
在 DESIGN.md 的变更历史中添加：
## 变更历史
### [日期] - [变更标题]
**变更内容**: 简述改了什么
**变更理由**: 为什么要改
**影响范围**: 影响哪些功能/模块
**决策依据**: 为何选择此方案（如适用）
自动触发时机
| 场景 | 触发条件 |
|---|---|
| 设计级变更 | 修改架构、接口、数据结构 |
| 重构完成 | 重构任务完成时 |
| 代码变更 > 30 行 | 较大规模代码修改 |
| 提交前 | 代码提交前检查 |
校验流程
1. 运行 change_analyzer.js 自动分析
2. 识别变更文件和受影响模块
3. 检查文档同步状态
4. 评估变更影响
5. 输出变更校验报告
校验报告格式
## 变更校验报告
### 变更概览
- 变更文件数: N
- 代码变更行数: +X / -Y
- 受影响模块: [模块列表]
### 文档同步状态
- README.md: ✓ 已同步 / ⚠️ 需更新
- DESIGN.md: ✓ 已同步 / ⚠️ 需更新
### 测试覆盖
- 测试文件变更: ✓ 有 / ⚠️ 无
### 结论
可提交 / 需补充文档后提交
What ships with it
1 file 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.
- 5d ago First seen · 141 lines · 65 tokens per session scan A 689a9c0573f6
verify-change is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 1,057 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to verify-change, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
pr-pending-feedback
Evaluate pending (unsubmitted) review comments on the current branch's PR and, after user confirmation, address each in a separate sub-agent and separate commit.