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 agentmods add skills/b33eep/claude-code-setup/standards-kotlinnpx skills add b33eep/claude-code-setup --skill standards-kotlingit clone --depth 1 https://github.com/b33eep/claude-code-setupWrote 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/b33eep/claude-code-setup/standards-kotlin)<a href="https://agentmods.dev/skills/b33eep/claude-code-setup/standards-kotlin"><img src="https://agentmods.dev/badge/skills/b33eep/claude-code-setup/standards-kotlin.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.09276 |
| Opus 5 | $0.00018 | $0.04638 |
| Sonnet 5 | $0.00007 | $0.01855 |
| Haiku 4.5 | $0.00004 | $0.00928 |
Grade A, and why
standards-kotlin 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 1,547 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kotlin Coding Standards
Core Principles
- Explicitness: Explicit code over implicit magic
- Readability: Readable code over clever tricks
- Null Safety: Embrace Kotlin's null safety system
- Immutability: Prefer
valovervar, immutable collections - Expressiveness: Use Kotlin's expressive features (data classes, sealed classes)
- DRY: Don't Repeat Yourself - but keep it simple
General Rules
- Prefer
valovervar: Immutability by default - Use data classes: For simple data holders
- Sealed classes/interfaces: For type-safe state modeling
- Early returns: Avoid deep nesting
- Descriptive names: Clear, meaningful names
- Minimal changes: Only change relevant code
- No over-engineering: Keep it simple
- Minimal comments: Self-explanatory code. Comments for "why", not "what"
Naming Conventions
| Element | Convention | Example |
|---|---|---|
| Classes | PascalCase | UserService, OrderRepository |
| Interfaces | PascalCase | UserRepository, PaymentProcessor |
| Functions | camelCase | getUserById, calculateTotal |
| Properties | camelCase | firstName, totalAmount |
| Constants | UPPER_SNAKE_CASE | MAX_RETRY_COUNT, DEFAULT_TIMEOUT |
| Packages | lowercase.dot.separated | com.example.service, com.example.repository |
| Files | PascalCase.kt | UserService.kt, OrderRepository.kt |
| Test Classes | ClassNameTest | UserServiceTest, OrderRepositoryTest |
| Test Functions | backtick names | `should return user when id exists` |
Project Structure
Gradle Kotlin DSL Project (Recommended)
myproject/
├── build.gradle.kts
├── settings.gradle.kts
├── gradle.properties
├── src/
│ ├── main/
│ │ ├── kotlin/
│ │ │ └── com/example/myapp/
│ │ │ ├── Application.kt # Main entry point
│ │ │ ├── config/
│ │ │ │ └── AppConfig.kt # Configuration
│ │ │ ├── domain/
│ │ │ │ └── User.kt # Domain models
│ │ │ ├── repository/
│ │ │ │ └── UserRepository.kt # Data access
│ │ │ ├── service/
│ │ │ │ └── UserService.kt # Business logic
│ │ │ └── api/
│ │ │ └── UserController.kt # REST endpoints
│ │ └── resources/
│ │ ├── application.conf
│ │ └── logback.xml
│ └── test/
│ ├── kotlin/
│ │ └── com/example/myapp/
│ │ ├── service/
│ │ │ └── UserServiceTest.kt
│ │ └── repository/
│ │ └── UserRepositoryTest.kt
│ └── resources/
│ └── application-test.conf
└── README.md
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.
- 4d ago First seen · 1,547 lines · 36 tokens per session scan A 9f10e47b2685
standards-kotlin is a skill published in the GitHub repository b33eep/claude-code-setup (56 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 9,276 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-08-30.
Other skills, from other repositories
swiftui-expert
Use when working in a native iOS/SwiftUI project - .swift files, an .xcodeproj or Package.swift, Xcode schemes, or mentions of SwiftUI, Swift 6, @Observable, SwiftData, NavigationStack, actors, or Swift Testing. Builds views and features, wires Observation-based state, fixes Swift 6 strict-concurrency errors, models…
kotlin-dev
Use when implementing any feature or bugfix in a Kotlin/Spring Boot service, covers layer conventions, idioms, testing, and observability.
kotlin-reviewer
Use when reviewing a Kotlin/Spring Boot pull request, systematic checklist covering architecture, idioms, testing, security, and observability.
swiftui-expert
This skill should be used when the user is building, reviewing, or debugging SwiftUI views and apps. Detects iOS and Swift version from the project. Covers creating views, state management with @Observable, NavigationStack routing, animations, accessibility, performance optimization, Liquid Glass adoption, design…
swiftui-max
Expert SwiftUI guidance for building UI on iOS, iPadOS, macOS, watchOS, tvOS, and visionOS. Use whenever writing, reviewing, refactoring, or debugging ANY SwiftUI code — views, view modifiers, layout, navigation (NavigationStack/SplitView, deep links), lists and scrolling, animation and transitions, state management…
swift-language
Comprehensive modern Swift (6.x) language expertise — concurrency, generics, ownership/performance, macros, API design, error handling, SwiftPM, C/C++/ObjC interop, cross-platform (Linux/Android/embedded/server), and Swift Testing. Use this skill whenever writing, reviewing, refactoring, or debugging ANY Swift code …