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 integration-contractsgit 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/integration-contracts)<a href="https://agentmods.dev/skills/s977043/river-review/integration-contracts"><img src="https://agentmods.dev/badge/skills/s977043/river-review/integration-contracts/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/integration-contracts"><img src="https://agentmods.dev/badge/skills/s977043/river-review/integration-contracts.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.01262 |
| Opus 5 | $0.00013 | $0.00631 |
| Sonnet 5 | $0.00005 | $0.00252 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
Service Integration & Contracts 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 7d 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 / 目的
- サービス間連携（API/イベント/メッセージング）の差分から、契約不備・責任境界の曖昧さ・障害時の未定義を早期に潰す。
Non-goals / 扱わないこと
- 連携方式の正解を断定しない（契約/運用/互換性の明確化に限定）。
- 実装レベルの細部（SDK、リトライ実装、キュー設定の調整など）。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分にサービス間連携・契約・インターフェイス・イベント定義に関するドキュメントまたはスキーマが含まれている
- inputContextにdiffが含まれている
ゲート不成立時の出力: NO_REVIEW: integration-contracts — サービス間連携/契約に関する差分がない
False-positive guards / 抑制条件
- 参照先の契約ドキュメントが明確で、差分が参照更新のみの場合は重複指摘しない。
Rule / ルール
- 先頭に要約を 1 行出す（producer/consumer、契約変更、互換性の要点）。
- 指摘は最大 8 件まで。互換性破壊、所有者不明、失敗時の振る舞い不明を優先。
- “追記テンプレ” を付けて、文書に落とせる形にする。
Checklist / 観点チェックリスト
- 契約（Contract）
- メッセージ/API のスキーマ、必須/任意、互換性ルール（追加は後方互換、削除は破壊的等）が明記されているか。
- バージョニング、deprecated 期間、移行ガイドがあるか。
- Owner と責任境界
- Producer/Consumer の Owner、SLA/SLO の前提、問い合わせ窓口があるか。
- どこまでが producer の責任で、どこから consumer かが書かれているか。
- 失敗時の振る舞い
- リトライ、冪等性、重複配信、順序、遅延、DLQ/再処理の前提があるか。
- エラーコード/失敗イベント/補償処理の方針があるか。
- ロールアウト/ロールバック
- 両対応期間（新旧契約）と、切替条件/ロールバック条件があるか。
- 段階リリース（feature flag 等）の前提があるか。
Output / 出力フォーマット
すべて日本語。<file>:<line>: <message> 形式で出力する。
- 先頭に要約を 1 行:
(summary):1: <producer/consumerと契約変更の要点> - 以降は指摘（最大 8 件）:
<message>に[severity=critical|major|minor|info]を含める。- 可能なら “追記テンプレ” を 1 行付ける。
追記テンプレ例:
Owner: producer=<team>, consumer=<team> / 互換性: <後方互換/破壊的> / 移行: <両対応期間>失敗時: retry=<回数/間隔>, idempotency=<キー>, DLQ=<扱い>, 補償=<方針>
評価指標（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.
- 7d ago First seen · 98 lines · 26 tokens per session scan A 584da6fcfa22
Service Integration & Contracts is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,262 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
testing-integration
Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.
Webhook Automation
Build and manage webhook-based integrations for real-time event processing and API connections.
api-contract-tester
Implement consumer-driven contract testing with Pact to ensure API compatibility.
Contract-First Testing
Contract-first testing approach using Pact, Spring Cloud Contract, or Dredd for ensuring API consumer-provider compatibility.
nodejs-backend
Node.js backend patterns: framework selection, layered architecture, TypeScript, validation, error handling, security, production deployment. Use when building REST APIs, Express/Fastify servers, microservices, or server-side TypeScript.
api-integrations
Expose external APIs to Falcon Foundry via OpenAPI specs. TRIGGER when user asks to "create an API integration", "adapt an OpenAPI spec for Foundry", "expose an API to workflows", "connect to a third-party API", or runs foundry api-integrations create. Also trigger when user has an OpenAPI/Swagger spec and wants it…