breach-encapsulation-naming

breach-encapsulation-naming is a skill for Claude Code, Codex from j5ik2o/okite-ai. It costs 218 tokens per session (2,331 once invoked), scanned A, original, MIT.

A guide to naming getters that expose data from a domain model after bypassing its usual encapsulation. Encapsulation means keeping an object's internal details protected behind its behavior.

In plain words
What is it for?
Use it when defining domain-model getters for persistence or JSON conversion in Java, Kotlin, TypeScript, Python, Go, or Rust.
Why use it?
It makes exceptional data access visible in code reviews and discourages using getters for ordinary business logic.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when defining domain-model getters for persistence or JSON conversion in Java, Kotlin, TypeScript, Python, Go, or Rust.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/j5ik2o/okite-ai/breach-encapsulation-naming
Install

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.

Any agent
npx skills add j5ik2o/okite-ai --skill breach-encapsulation-naming
Clone the repo
git clone --depth 1 https://github.com/j5ik2o/okite-ai

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for breach-encapsulation-naming

README.md
[![agentmods](https://agentmods.dev/badge/skills/j5ik2o/okite-ai/breach-encapsulation-naming/github.svg)](https://agentmods.dev/skills/j5ik2o/okite-ai/breach-encapsulation-naming)
Your own site
<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/breach-encapsulation-naming"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/breach-encapsulation-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.

agentmods 80×15 button for breach-encapsulation-naming

Your own site · 80×15
<a href="https://agentmods.dev/skills/j5ik2o/okite-ai/breach-encapsulation-naming"><img src="https://agentmods.dev/badge/skills/j5ik2o/okite-ai/breach-encapsulation-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 218 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,331 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00218 $0.02331
Opus 5 $0.00109 $0.01166
Sonnet 5 $0.00044 $0.00466
Haiku 4.5 $0.00022 $0.00233

Measured 9d ago against content hash bb9f017f3464, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

breach-encapsulation-naming 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 9d 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.

skills/breach-encapsulation-naming/SKILL.md · 268 lines

How it starts

The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Breach Encapsulation Naming

getterを作るなら「カプセル化を破っている」と名前で叫べ。

核心原則

ドメインモデルのgetterには breachEncapsulationOf プレフィックスを付与し、カプセル化を破っていることを明示する。

アプローチ 特徴 効果
通常のgetter (getName()) 気軽に使える 濫用されやすい
明示的なgetter (breachEncapsulationOfName()) 使用時に「破っている」と意識 濫用を抑制

なぜこの命名規約が必要か

ジレンマ

  1. Tell Don't Ask原則: getterを使わず、オブジェクトに命じるべき
  2. 現実の制約: 永続化やJSON変換ではgetterが必要
  3. 問題: getterがあると、ビジネスロジックでも使ってしまう

解決策

getterを「長くて目立つ名前」にすることで:

  • 使うたびに「これは例外的な使用だ」と意識させる
  • コードレビューで発見しやすくなる
  • 静的解析ツールで検出可能になる

命名パターン

基本形式

breachEncapsulationOf<PropertyName>()

言語別の例

// Java
public String breachEncapsulationOfName() { return this.name; }
public Money breachEncapsulationOfPrice() { return this.price; }
// Kotlin
fun breachEncapsulationOfName(): String = name
fun breachEncapsulationOfPrice(): Money = price
// TypeScript
breachEncapsulationOfName(): string { return this.name; }
breachEncapsulationOfPrice(): Money { return this.price; }
# Python
def breach_encapsulation_of_name(self) -> str:
    return self._name
// Go
func (u *User) BreachEncapsulationOfName() string { return u.name }
// Rust
pub fn breach_encapsulation_of_name(&self) -> &str { &self.name }

適用判断フロー

getterが必要か?
    ↓
├─ NO → getterを作らない(Tell Don't Ask)
│
└─ YES → 対象は?
          │
          ├─ 値オブジェクト → 通常のアクセサでOK
          │   (イミュータブルかつ振る舞いが限定的なため)
          │   例: Money.amount(), UserId.value()
          │
          └─ エンティティ → breachEncapsulationOf を使用
                            │
                            └─ なぜ必要?
                                ├─ 永続化/シリアライズ → ✅ 許容
                                ├─ 表示/UI → ✅ 許容
                                ├─ テスト → ✅ 許容
                                └─ ビジネスロジック → ❌ Tell パターンに変換

値オブジェクト vs エンティティ

種類 特徴 getter方針
値オブジェクト イミュータブル、等価性で識別 通常のアクセサ可(amount(), value()
エンティティ ミュータブル、IDで識別 breachEncapsulationOf を使用

Read the full file on GitHub · 268 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 9d ago First seen · 268 lines · 218 tokens per session scan A bb9f017f3464

Subscribe to this mod's changes

breach-encapsulation-naming is a skill published in the GitHub repository j5ik2o/okite-ai (81 stars, last pushed 4mo ago), licensed MIT. It adds 218 tokens to every session and 2,331 once invoked, about $0.0011 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-01.

Related

Other skills, from other repositories

hr-onboarding

A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".

nexu-io/open-design · 62 tokens

book-mirror

Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…

garrytan/gbrain · 138 tokens

miniapp

Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.

yc-software/qm · 25 tokens

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

companion-inc/feynman · 63 tokens

deck-course-module

A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.

nexu-io/html-anything · 25 tokens

master-yinguang

A reference-based assistant for questions about Yinguang and Pure Land Buddhism, a Buddhist tradition focused on faith, ethical living, and practice connected with rebirth in the Pure Land. It can answer in Yinguang’s historical teaching style.

xr843/Master-skill · 274 tokens