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 ubiquitous-language-naminggit 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/ubiquitous-language-naming)<a href="https://agentmods.dev/skills/s977043/river-review/ubiquitous-language-naming"><img src="https://agentmods.dev/badge/skills/s977043/river-review/ubiquitous-language-naming/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/ubiquitous-language-naming"><img src="https://agentmods.dev/badge/skills/s977043/river-review/ubiquitous-language-naming.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.00036 | $0.01014 |
| Opus 5.5 | $0.00014 | $0.00406 |
| Sonnet 5.5 | $0.00007 | $0.00203 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
Ubiquitous Language Naming 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 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: なし Why: 差分内の識別子をドメイン用語の一貫性という単一観点で評価するレビュースキル
Goal / 目的
- ドメイン概念の命名ドリフト（同一概念の別名、別概念の同名）が差分から混入するのを防ぐ。
- diff 単体で安全に動作し、plan / ADR が無いリポジトリでも ddd pack の空振りを防ぐ。
Non-goals / 扱わないこと
- 集約境界・コンテキスト境界の設計判断（
bounded-context-languageが artifact ベースで扱う）。 - primitive obsession / brand 型の検出（
type-driven-designに委譲する）。 - 一般的な命名の良し悪し（広すぎる名前等）。ドメイン用語の 一貫性 のみを見る。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分にドメイン語彙を含む識別子（型名・関数名・プロパティ名）の追加または改名が含まれている
- diff コンテキストが利用可能である
ゲート不成立時の出力: NO_REVIEW: ubiquitous-language-naming — ドメイン識別子の変更なし
補足: plan / ADR / 用語集が利用可能な場合はそれを正とし、無い場合は 差分周辺の既存コードの語彙 を正とする（degraded mode）。
False-positive guards / 抑制条件
- 外部 API / ライブラリ由来の名前（SDK の型名等）はプロジェクトの用語と一致しなくても指摘しない。
- テストダブル・fixture 内の意図的な別名は指摘しない。
- 単数形/複数形・大文字小文字のみの揺れで、文脈上意味が同一と判断できる場合は質問に留める。
Rule / ルール
- 同一概念が差分内・周辺コードで別名になっていないか（例:
CustomerとClientの混在）。 - 既存の別概念と同じ名前を新規に割り当てていないか（例: 課金の
Accountと認証のAccount）。 - ドメイン用語の翻訳揺れ（和英混在で同一概念を指す等）が新規導入されていないか。
Evidence / 根拠の取り方
- 指摘は
<file>:<line>で差分に紐づけ、衝突相手（既存の識別子と位置）を併記する。 - 用語の正が判断できない場合は断定せず、
questionsとして「どちらの用語に揃えるか」を返す。
Output / 出力（短文版の推奨）
コメントは日本語で返す。
- Finding: どの用語がどこでドリフトしたか（1文）
- Impact: ドメイン理解・検索性への影響（短く）
- Fix: 揃える先の用語と最小の改名案
例:
src/billing/invoice.ts:24: 既存の Customer と同概念の Client を新規導入。用語が分裂し検索性が低下。Fix: Customer に統一
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 · 75 lines · 36 tokens per session scan A e89b3eb9d2c0
Ubiquitous Language Naming Consistency is a skill published in the GitHub repository s977043/river-review (7 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,014 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
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-fix-all
Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…
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…
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.