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 s977043/river-review --skill change-communicationgit clone --depth 1 https://github.com/s977043/river-reviewWrote 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/s977043/river-review/change-communication)<a href="https://agentmods.dev/skills/s977043/river-review/change-communication"><img src="https://agentmods.dev/badge/skills/s977043/river-review/change-communication/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/s977043/river-review/change-communication"><img src="https://agentmods.dev/badge/skills/s977043/river-review/change-communication.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.00026 | $0.01188 |
| Opus 5.5 | $0.00010 | $0.00475 |
| Sonnet 5.5 | $0.00005 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
Architecture Change Communication 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 1mo 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.
What it actually says
Pattern declaration
Primary pattern: Reviewer Secondary patterns: Inversion Why: 設計変更の影響範囲・通知計画・非推奨措置をチェックリスト型で評価し、コミュニケーション漏れを防ぐ
Goal / 目的
- 設計変更の差分から、影響範囲・通知経路・非推奨措置を共有するコミュニケーション計画が抜け落ちていないかをチェックする。
Non-goals / 扱わないこと
- 内部通知ツール（Slack/Teams）のテンプレ作成や運用作業そのもの。
- 個別チームの予定調整（ただし通知対象に入るべきステークホルダーは指摘する）。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分に設計ドキュメント（アーキテクチャ/ADR/設計書）の変更がある
- 差分にアーキテクチャ変更・API変更・非推奨化など影響範囲を伴う記述の追加または変更がある
- inputContextにdiffが含まれている
ゲート不成立時の出力: NO_REVIEW: change-communication — コミュニケーション計画が必要な設計変更が検出されない
False-positive guards / 抑制条件
- すでに別 ADR/通知チャネルで整備されており、差分がその参照のみであれば重複指摘を避ける。
Rule / ルール
- 先頭に要約を 1 行出す（影響範囲・通知・非推奨/移行の要点）。
- 指摘は最大 8 件。ステークホルダー漏れ、通知対象不明、移行/非推奨の曖昧さを優先。
- 可能なら「通知文/説明テンプレ」を添える（貼れる短文）。
Checklist / 観点チェックリスト
- 影響範囲
- 変更が影響するサービス/チーム/ドメインを列挙しているか。
- オーナー/責任者（Team/Role）が明記されているか。
- 通知計画
- 変更を知らせるチャネル（release notes, mailing list, status page 等）が決まっているか。
- スケジュール（いつ通知し、いつ施行するか）があるか。
- 非推奨・移行
- 旧バージョン/機能の非推奨状況と移行締切があるか。
- 互換性の切り分け（どのクライアント/サービスが動かなくなるか）が説明されているか。
- 継続的整合
- ドキュメント/ADR/図の更新が必要な箇所が TODO/追跡対象としてリストされているか。
- コミュニケーションの経路（誰が更新するか）を明示しているか。
Output / 出力フォーマット
すべて日本語。<file>:<line>: <message> 形式で出力。
- 先頭に要約行:
(summary):1: <影響範囲/通知/非推奨の要点> - 指摘（最大8件）:
[severity=critical|major|minor|info]を含める。- 可能なら「通知テンプレ」等を追加。
例:
docs/architecture/change.md:42: [severity=major] 公開API影響が未通知。Fix: 12月14日 15:00に release-notes へ通知予定と明記。
評価指標（Evaluation）
- 合格: 影響範囲・通知計画・移行方針に抜けがないかを差分に紐づく形で指摘し、アクションに結びつく遷移案がある。
- 不合格: 一般論やオペレーションの詳細、差分と無関係なステークホルダー批判。
人間に返す条件（Human Handoff）
- 組織的なポリシー変更や交渉が必要な場合は人間レビューへ。
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.
- 1mo ago First seen · 95 lines · 26 tokens per session scan A f08067d9391d
Architecture Change Communication is a skill published in the GitHub repository s977043/river-review (7 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,188 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-09-03.
Other skills, from other repositories
punchcard
Architecture-level design review of a code change: module boundaries, dependency direction, data model, error paths, cost of the next change — never naming, formatting, or anything a linter catches. Use when the user invokes /punchcard, says 'punchcard review', or asks for any design, architecture, or structural…
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…
run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…
sync-skill-cache
Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills//SKILL.md or guide/shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is…
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.