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-traceabilitygit 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-traceability)<a href="https://agentmods.dev/skills/s977043/river-review/architecture-traceability"><img src="https://agentmods.dev/badge/skills/s977043/river-review/architecture-traceability/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-traceability"><img src="https://agentmods.dev/badge/skills/s977043/river-review/architecture-traceability.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.00032 | $0.01213 |
| Opus 5 | $0.00016 | $0.00607 |
| Sonnet 5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
Architecture Traceability & Consistency 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.
What it actually says
Pattern declaration
Primary pattern: Reviewer Secondary patterns: Inversion Why: ADR・図・仕様間の食い違いを検出し、設計ドリフトの早期発見とトレーサビリティ確保を行う。
Goal / 目的
- 設計変更の差分から、ADR・図・仕様の “食い違い” を早期に発見し、設計ドリフトを抑える。
Non-goals / 扱わないこと
- 設計の正解を断定しない（整合性とトレーサビリティの不足を指摘する）。
- 実装の詳細レビュー（コード品質やテスト実装の指摘）。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分にアーキテクチャ/設計関連ファイル（
docs/architecture/,docs/adr/,*design*.md,*architecture*.md,*.adr,*c4*,*diagram*）が含まれている - 差分に意思決定・構成要素・契約に関する記述の追加・変更が含まれている
- inputContextに
diffが含まれている
ゲート不成立時の出力: NO_REVIEW: architecture-traceability — 設計トレーサビリティに関連するドキュメントの変更なし
False-positive guards / 抑制条件
- 明確に “既存 ADR への参照追加のみ” で、整合性が保たれている場合は重複指摘しない。
Rule / ルール
- 先頭に要約を 1 行出す（変更された決定/構成要素/契約の要点）。
- 指摘は最大 8 件まで。矛盾・参照切れ・未更新の決定事項を優先。
- 可能なら “追記案（貼れる形）” を付ける。
Checklist / 観点チェックリスト
- ADR との整合
- 設計変更が ADR の決定事項と矛盾していないか（または “ADR を更新する” と明記されているか）。
- 代替案/却下理由/トレードオフが変わったのに ADR が更新されていない箇所がないか。
- 図（C4/シーケンス等）との整合
- 図に現れるコンポーネント/依存/データフローが本文と一致しているか。
- 重要な変更（境界/依存/責務）に対して図の更新が漏れていないか。
- 仕様との整合
- API/イベント/データ契約の変更が、仕様書や参照リンクに反映されているか。
- 用語・命名（コンポーネント名/責務名）が文書間で揺れていないか。
- ドリフトの扱い
- 未更新や未決事項がある場合、リスクとして明示され、フォローアップ（TODO/期限/担当）があるか。
Output / 出力フォーマット
すべて日本語。<file>:<line>: <message> 形式で出力する。
- 先頭に要約を 1 行:
(summary):1: <整合性/トレーサビリティの要点> - 以降は指摘（最大 8 件）:
<message>に[severity=critical|major|minor|info]を含める。- 可能なら “追記案” を 1 行付ける（例:
この変更に対応する ADR=... を更新/追加）。
評価指標（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.
- 5d ago First seen · 92 lines · 32 tokens per session scan A 1ff78ab1e3c1
Architecture Traceability & Consistency is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,213 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-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…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.