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 availability-architecturegit 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/availability-architecture)<a href="https://agentmods.dev/skills/s977043/river-review/availability-architecture"><img src="https://agentmods.dev/badge/skills/s977043/river-review/availability-architecture/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/availability-architecture"><img src="https://agentmods.dev/badge/skills/s977043/river-review/availability-architecture.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.00029 | $0.01126 |
| Opus 5.5 | $0.00012 | $0.00450 |
| Sonnet 5.5 | $0.00006 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
Availability & Resilience Architecture 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 / 扱わないこと
- 個別インフラ製品（クラウドプロバイダ等）の設定レビュー。
- 実装コードやライブラリのパフォーマンス最適化。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分に設計ドキュメント（アーキテクチャ/ADR/設計書）の変更がある
- 差分に可用性・冗長性・復旧・容量に関わる記述の追加または変更がある
- inputContextにdiffが含まれている
ゲート不成立時の出力: NO_REVIEW: availability-architecture — 可用性設計に関わる変更が検出されない
False-positive guards / 抑制条件
- ドキュメントが PoC/実験系で、本番可用性を担保する責務が無いと明記されている場合は強度を下げる。
Rule / ルール
- 要点を 1 行要約（可用性目標/フェイルオーバー/容量の要点）。
- 指摘は最大 8 件。SLO・復旧手順・容量余裕・劣化モードを優先。
- 可能なら「運用手順テンプレ」を付ける。
Checklist / 観点チェックリスト
- 可用性目標と測定
- 重要パスの SLI/SLO（p99, error rate 等）が定義されているか。
- 計測方法・除外条件・観測範囲があるか。
- フェイルオーバーと復旧
- 障害時の切り替え手順（自動/手動）と判定メトリクスがあるか。
- リカバリタイム（RTO）・リカバリポイント（RPO）の目標があるか。
- 容量と冗長
- トラフィック/データ量のピーク前提とスケール戦略があるか。
- データセンタ/リージョン冗長の扱いや、段階的スケール案があるか。
- 劣化モードと観測性
- 劣化時の挙動（バックプレッシャー、Graceful degradation）が説明されているか。
- 異常時に見るべきメトリクス/ダッシュボード/アラートが列挙されているか。
Output / 出力フォーマット
日本語で <file>:<line>: <message> 形式。
(summary):1: <可用性/復旧/容量の要点>を先頭に。- 指摘には
[severity=critical|major|minor|info]を含め、可能なら追記案を一行付加。
追記テンプレ例:
SLO: service=<>, metric=p99 latency, target=<>, measurement=<dash>Failover: trigger=<>, action=<>, verification=<logs>Capacity: peak=<>, headroom=<>, scaling=<policy>
評価指標（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.
- 1mo ago First seen · 95 lines · 29 tokens per session scan A 1cbab5cdb010
Availability & Resilience Architecture is a skill published in the GitHub repository s977043/river-review (7 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,126 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
infrastructure-validation
Validates infrastructure-as-code with tool chains and checks for common mistakes. Use when working with Terraform (.tf, .tfvars), Ansible (playbooks, roles, inventory), Docker (Dockerfile, docker-compose.yml), Kubernetes (manifests, Helm charts), or CloudFormation. Also use when running terraform plan/apply, building…
terraform
Terraform and OpenTofu configuration, modules, testing, state management, and HCL review. Use for "terraform module", "terraform test", "infrastructure as code", "IaC", "HCL", "tfvars", "terraform plan", "terraform apply", "OpenTofu", "tftest", or multi-environment patterns.
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…