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 architecture-boundariesgit 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/architecture-boundaries)<a href="https://agentmods.dev/skills/s977043/river-review/architecture-boundaries"><img src="https://agentmods.dev/badge/skills/s977043/river-review/architecture-boundaries/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/architecture-boundaries"><img src="https://agentmods.dev/badge/skills/s977043/river-review/architecture-boundaries.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.00027 | $0.01267 |
| Opus 5 | $0.00014 | $0.00633 |
| Sonnet 5 | $0.00005 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
Architecture Boundaries & Dependencies 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 8d 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 / 扱わないこと
- アーキの正解を断定しない（境界/責務/依存関係の “記述の質” に限定）。
- 実装レベルの設計（クラス設計や関数分割）への立ち入り。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分にアーキテクチャ/設計ドキュメント（
docs/architecture/,docs/adr/,*architecture*.md,*design*.md,*.adr,*c4*,*diagram*）が含まれている - 差分にコンポーネントの境界・責務・依存関係に関する記述の追加・変更が含まれている
- inputContextに
diffが含まれている
ゲート不成立時の出力: NO_REVIEW: architecture-boundaries — 境界/依存に関する設計ドキュメントの変更なし
False-positive guards / 抑制条件
- 既に参照先（ADR/図/既存ルール）で明確な場合は、重複指摘しない。
Rule / ルール
- 先頭に要約を 1 行出す（追加/変更されたコンポーネントと依存の要点）。
- 指摘は最大 8 件まで。境界の曖昧さ、依存方向の逆流、責務の過密、影響範囲の未整理を優先。
- 可能な限り “追記案（貼れる形）” を付ける。
Checklist / 観点チェックリスト
- 境界と責務
- コンポーネント/モジュールの責務が 1〜3 行で説明されているか。
- “どこまでが担当範囲か（Non-goals）” が明記されているか。
- Owner（チーム/担当）や運用責任が曖昧でないか。
- 依存方向
- 依存の向きが一貫しているか（例: 上位→下位、Domain→Infrastructure など）。
- 依存の理由（なぜ必要か）が書かれているか。
- 双方向依存や循環依存を生む構造になっていないか。
- 変更影響
- 変更で影響を受ける利用者/サービス/データ/運用が列挙されているか。
- 互換性（API/イベント/データ）と移行の前提が明記されているか。
- 境界を跨ぐ契約
- インターフェース（API/イベント/バッチ入出力）の契約がドキュメント化されているか。
- エラーモデル/リトライ/冪等性など、跨ぎ方のルールがあるか。
Output / 出力フォーマット
すべて日本語。<file>:<line>: <message> 形式で出力する。
- 先頭に要約を 1 行:
(summary):1: <境界/依存/影響の要点> - 以降は指摘（最大 8 件）:
<message>に[severity=critical|major|minor|info]を含める。- 可能なら “追記案” を 1 行付ける（例:
責務: ... / Non-goals: ... / 依存理由: ...）。
評価指標（Evaluation）
- 合格基準: 差分に紐づく境界/依存/影響の抜けが、優先度付きで指摘され、追記案がある。
- 不合格基準: 差分と無関係な一般論、根拠のない断定、指摘の洪水。
人間に返す条件（Human Handoff）
- トレードオフが組織/ロードマップに影響する場合は人間の設計レビューへ返す。
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.
- 8d ago First seen · 94 lines · 27 tokens per session scan A 5f76a4162f90
Architecture Boundaries & Dependencies is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,267 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
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…
code-quality-principles
Applies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.
aesthetic-instrument
A committed aesthetic in the sense of skills/committed-aesthetic/SKILL.md: every rule below is checkable, and every value was read out of the source — packages/board/public/index.html and greatcto-site/styles.css — rather than chosen to write this document.
committed-aesthetic
How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when…
design-reviewer
Use after AC and before RED for any wave that ships UI. Performs component API audit against installed dist files, produces per-route mockup, defines visual ACs, flags design-system gaps. Output written to .wave/dr.md.