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 event-driven-semanticsgit 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/event-driven-semantics)<a href="https://agentmods.dev/skills/s977043/river-review/event-driven-semantics"><img src="https://agentmods.dev/badge/skills/s977043/river-review/event-driven-semantics/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/event-driven-semantics"><img src="https://agentmods.dev/badge/skills/s977043/river-review/event-driven-semantics.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.00033 | $0.01280 |
| Opus 5 | $0.00016 | $0.00640 |
| Sonnet 5 | $0.00007 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
Event-Driven Semantics & Delivery Guarantees 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: イベント駆動設計の差分から配信保証・冪等性・スキーマ進化の抜けをレビューし、障害シナリオを逆照射して設計の堅牢性を検証する。
Goal / 目的
- イベント駆動設計の差分から、配信保証・順序・冪等性・再処理/リプレイの未定義による事故を減らす。
Non-goals / 扱わないこと
- メッセージ基盤の選定（Kafka/SQS 等）の是非の断定。
- 実装レベルの consumer コードやライブラリ選定。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分にイベント駆動・メッセージング・キュー・ストリーム関連のドキュメントまたはスキーマが含まれている
- inputContextにdiffが含まれている
ゲート不成立時の出力: NO_REVIEW: event-driven-semantics — イベント駆動設計関連の差分がない
False-positive guards / 抑制条件
- 契約が別ドキュメントで管理され、参照が明確な場合は重複指摘しない。
Rule / ルール
- 先頭に要約を 1 行出す（新規/変更イベントと consumer 影響の要点）。
- 指摘は最大 8 件まで。順序/重複/再処理で壊れる設計を優先。
- 可能なら “追記テンプレ” を付ける（文書に貼れる形）。
Checklist / 観点チェックリスト
- 配信保証と重複
- 配信保証（at-least-once/at-most-once/exactly-once の前提）が明記されているか。
- 重複配信を前提にした冪等性（idempotency key、dedupe）の設計があるか。
- 順序とキー
- 順序保証の前提（partition key、同一キー内のみ順序等）が明示されているか。
- 乱順/遅延到着の扱い（reorder window、最終状態の決め方）があるか。
- スキーマ進化
- 互換性ルール（追加は後方互換、削除は破壊的等）と versioning があるか。
- deprecated 期間と移行手順（producer/consumer の段階更新）があるか。
- 再処理/リプレイ
- リプレイ/backfill の方針（いつ、どこから、どれくらい）があるか。
- DLQ/poison message の扱いと再処理手順があるか。
- 観測性
- eventId/correlationId、consumer lag、失敗率などの監視前提があるか。
Output / 出力フォーマット
すべて日本語。<file>:<line>: <message> 形式で出力する。
- 先頭に要約を 1 行:
(summary):1: <イベント契約/保証/移行の要点> - 以降は指摘（最大 8 件）:
<message>に[severity=critical|major|minor|info]を含める。- 可能なら “追記テンプレ” を 1 行付ける。
追記テンプレ例:
保証: at-least-once / 冪等性: key=<>, dedupe=<>, 重複時: <扱い>順序: key=<>, 保証範囲=<同一キー内のみ> / 乱順: <扱い>互換性: <後方互換/破壊的> / version=<>, 移行: <両対応期間>
評価指標（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 · 102 lines · 33 tokens per session scan A c0b43361d7b0
Event-Driven Semantics & Delivery Guarantees is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,280 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
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…
application-patterns
Architecture pattern selection, folder structures, coding conventions, error handling, testing strategies, and platform-specific patterns for structuring application code.
python-services
Python patterns for CLI tools, async parallelism, and backend services. Use when building CLI apps, async/parallel Python, FastAPI services, background jobs, or configuring Python project tooling (uv, ruff, ty).
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.
backend-clean-architecture
Use this skill when the user asks 'where does this code go', 'what layer', 'clean architecture', 'hexagonal', 'ports and adapters', 'domain layer', 'application layer', 'infrastructure layer', 'should this be in service or repository', or when designing or reviewing backend code organization. This skill enforces…
php-laravel
Modern PHP 8.2+ and Laravel patterns: architecture, Eloquent, queues, Pest testing. Use when asked to "write PHP", "build a Laravel app", "fix Eloquent query", "add a queue job", "write a Pest test", or mentions PHP, Laravel, Eloquent, Blade, artisan, or migrations.