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 amadeus-dlc/amadeus --skill breach-encapsulation-naminggit clone --depth 1 https://github.com/amadeus-dlc/amadeusWrote 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/amadeus-dlc/amadeus/breach-encapsulation-naming)<a href="https://agentmods.dev/skills/amadeus-dlc/amadeus/breach-encapsulation-naming"><img src="https://agentmods.dev/badge/skills/amadeus-dlc/amadeus/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.
<a href="https://agentmods.dev/skills/amadeus-dlc/amadeus/breach-encapsulation-naming"><img src="https://agentmods.dev/badge/skills/amadeus-dlc/amadeus/breach-encapsulation-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.00082 | $0.00406 |
| Opus 5 | $0.00041 | $0.00203 |
| Sonnet 5 | $0.00016 | $0.00081 |
| Haiku 4.5 | $0.00008 | $0.00041 |
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 10d 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
Breach Encapsulation Naming
Make unavoidable state exposure loud. Domain objects should express behavior first; when an accessor is required for persistence, serialization, debugging, or tests, name it as an explicit encapsulation breach.
Workflow
-
Classify every requested accessor by consumer: domain behavior, persistence, serialization, tests, framework glue, or presentation.
-
Replace domain-behavior access with Tell Don't Ask methods on the object that owns the data.
-
For unavoidable exposure, use
breachEncapsulationOfX()or the idiomatic local equivalent such asbreach_encapsulation_of_x. -
Keep exposed values immutable or defensively copied.
-
Add a review note explaining why the breach is tolerated and which callers may use it.
Review Checks
-
Ordinary getters on entities and aggregates need justification.
-
Accessors used by domain logic are design smells; move the decision to the model.
-
Framework-required access should be isolated in adapters, serializers, mappers, or repository glue.
-
Tests may use breach accessors, but assertions should still prefer observable behavior when possible.
References
Read references/patterns.md for language-specific naming and migration examples.
Detailed Reference
For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.
Output
Return the accessor classification, recommended names, any Tell Don't Ask replacements, and the smallest migration path.
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.
- 10d ago First seen · 44 lines · 82 tokens per session scan A d85519d169d9
breach-encapsulation-naming is a skill published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 19d ago), licensed Apache-2.0. It adds 82 tokens to every session and 406 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
agent-hephaestus
UI, accessibility, and interaction-quality review.
Architecture Traceability & Consistency
Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.