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 agentmods add skills/telagod/code-abyss/analyzing-changesnpx skills add telagod/code-abyss --skill analyzing-changesgit clone --depth 1 https://github.com/telagod/code-abyssWhat 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 | $0.00048 | $0.00956 |
| Opus 5 | $0.00024 | $0.00478 |
| Sonnet 5 | $0.00010 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
analyzing-changes 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 yesterday.
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.
What it actually says
变更校验关卡
看清「改了什么、影响哪里、文档是否跟上」——是变更的体检，不是审查替代品。
何时使用
| 场景 | 跑 | 判据 |
|---|---|---|
| 提交前（任何代码改动） | ✅ | 默认门禁 |
| 重构完成 | ✅ | 评估辐射面 |
| 设计级改动 | ✅ | DESIGN.md 是否同步 |
| PR review | ✅ | 替代手工 diff 计数 |
| 跨模块大改 | ✅ | 看依赖图是否成环 |
| 紧急 hotfix | ⚠ | 跑，但允许文档同步延后到稳定后 |
三种模式
| 模式 | 时机 | 用途 |
|---|---|---|
working (默认) |
写代码过程中 | 自检，看「我现在的工作面有哪些待整理」 |
staged |
git add 后、commit 前 |
提交闸，看「这一 commit 的合理性」 |
committed |
commit 完成后 | review，看「上一段历史改了哪些范围」 |
警告判定
| 警告 | 触发 | 处置 |
|---|---|---|
| 代码 >50 行 而 DESIGN.md 未更新 | 设计层面变化未留痕 | 补 DESIGN.md「改了什么/为何」段 |
| 代码 >30 行 而无测试更新 | 测试覆盖滞后 | 补单测/集成测；或在 PR 注明「该路径已有 E2E 覆盖」 |
| 新增文件而 README.md 未更新 | 用户视角文档滞后 | 补模块入口说明 |
| 配置变更未记录 | 部署可能踩坑 | CHANGELOG / DESIGN 留迁移说明 |
| 删除文件 | 引用可能未清理 | 全仓 grep 文件名/导出符号 |
解读输出
工具产出三类信号：
- 文件分类 — 自动分代码/文档/测试/配置；用于判断「是否纯文档变更」
- 模块识别 — 把变更聚到模块边界；用于判断「跨模块改动」
- 影响评估 — 行数 + 文件数；用于判断「改动是否需要拆 PR」
拆 PR 的判据（基于 commit 角度）：
- 跨 ≥3 模块且无统一主题 → 拆
- 单 commit >500 行非生成代码 → 拆
- 一次同时改架构 + 实现 + 文档 → 通常合理（同主题）
与其他 skill 联动
- 设计级变更 → 触发 verifying-modules 看新模块文档完整性
- 安全相关变更 → 触发 analyzing-security
- 重构 → 触发 checking-code-quality 防退化
使用
node scripts/change_analyzer.js # working（默认）
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 # CI 用
人工复核
工具给信号，人下结论。先读受影响模块 README/DESIGN，确认：
- 职责边界是否仍清晰
- 设计决策是否仍成立
- 测试是否覆盖新路径
设计级改动须于 DESIGN.md 留痕：改了什么、为何改、影响何处。三段缺一不可。
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.
- yesterday First seen · 80 lines · 48 tokens per session scan A 10f250845b1a
analyzing-changes is a skill published in the GitHub repository telagod/code-abyss (240 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 956 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-30.
Other skills, from other repositories
codexkit-a-b-test-planner
Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.
codexkit-api-design-reviewer
Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.
codexkit-architecture-decision-writer
Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.
codexkit-audit-readiness-checker
Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when…
codexkit-business-case-writer
Write structured business cases with problem framing, options analysis, financial modeling (NPV/ROI/Payback), risk assessment, and implementation roadmap. Follows HBR business case structure. Use when seeking budget approval, proposing new initiatives, or justifying investment decisions.
codexkit-campaign-brief-writer
Write agency-standard creative briefs for marketing campaigns. Structure Background, Objective (SMART), Target Audience persona, Key Message, Mandatories, KPIs, Timeline, and Budget Allocation. Use when briefing agencies, creative teams, or internal marketing on a new campaign.