kora-testing-junit-kotlin

kora-testing-junit-kotlin is a skill for Claude Code from kora-projects/kora-skills. It costs 64 tokens per session (3,573 once invoked), scanned A, original, Apache-2.0.

A JUnit 5 testing add-on for Kotlin services built with Kora, a framework that generates the application’s dependency graph at compile time.

In plain words
What is it for?
Use it for component tests, MockK-based replacements, configuration and graph modifiers, coroutine tests, test-only repositories, and PostgreSQL Testcontainers in a Kora application.
Why use it?
It tests real generated application components instead of relying on a runtime container, while allowing selected dependencies or configuration to be replaced for tests.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is **Kora sub-skill — obey the [kora-v1 meta rules](../../SKILL.md) on every task:** **R0** ensure `.kora-agent/` docs+examples are cloned · **R1** read this sub-s.

Part of the kora-v1 plugin — 41 skills shipped together

Good fit Use it for component tests, MockK-based replacements, configuration and graph modifiers, coroutine tests, test-only repositories, and PostgreSQL Testcontainers in a Kora application.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/kora-projects/kora-skills
agentmods
npx agentmods add skills/kora-projects/kora-skills/kora-testing-junit-kotlin

Made for: Claude Code.

Or install kora-v1, the plugin that ships this one along with the rest of its 41 skills.

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 kora-testing-junit-kotlin

README.md
[![agentmods](https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-testing-junit-kotlin/github.svg)](https://agentmods.dev/skills/kora-projects/kora-skills/kora-testing-junit-kotlin)
Your own site
<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-testing-junit-kotlin"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-testing-junit-kotlin/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 kora-testing-junit-kotlin

Your own site · 80×15
<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-testing-junit-kotlin"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-testing-junit-kotlin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,573 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.00064 $0.03573
Opus 5.5 $0.00026 $0.01429
Sonnet 5.5 $0.00013 $0.00715
Haiku 4.5 $0.00006 $0.00357

Measured 2mo ago against content hash a6e2d9c58b00, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kora-testing-junit-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 2mo 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.

plugins/kora-v1/skills/kora-testing-junit-kotlin/SKILL.md · 375 lines

How it starts

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

Kora Testing JUnit (Kotlin)

Kora sub-skill — obey the kora-v1 meta rules on every task: R0 ensure .kora-agent/ docs+examples are cloned · R1 read this sub-skill before writing code · R2 Kora APIs only — no Spring/Micronaut/Quarkus, no invented annotations or config keys · R3 journal any incorrect Kora usage. Add comments/Javadoc only if asked.

In-process JUnit 5 tests that build a real Kora application Graph at compile time and inject its components into the test. @KoraAppTest reads a @KoraApp interface, builds only the slice of the Graph reachable from the requested @TestComponents, and hands those components to the test. There is no reflection-based runtime container — the same generated *Graph code used in production runs in the test.

Read this first when:

  • writing the first component test for a Kora Kotlin service,
  • mocking a graph dependency with @MockK + @TestComponent,
  • overriding config via KoraAppTestConfigModifier,
  • adding or replacing a component via KoraAppTestGraphModifier,
  • adding test-only repositories through the TestApplication submodule pattern,
  • wiring a PostgreSQL Testcontainer into a @KoraAppTest.

Quick Start

1. Dependencies (build.gradle.kts)

All Kora artifacts inherit their version from the kora-parent BOM — never pin a ru.tinkoff.kora:* version individually.

dependencies {
    // BOM already applied in the project (ru.tinkoff.kora:kora-parent)
    ksp("ru.tinkoff.kora:symbol-processors")

    testImplementation(platform("org.junit:junit-bom:5.13.4"))
    testImplementation("org.junit.jupiter:junit-jupiter")
    testImplementation("ru.tinkoff.kora:test-junit5")

    // Kotlin-idiomatic mocking
    testImplementation("io.mockk:mockk:1.13.11")
}

tasks.test {
    useJUnitPlatform()
    testLogging {
        showStandardStreams = true
        events("passed", "skipped", "failed")
        exceptionFormat = org.gradle.api.tasks.testing.logging.TestExceptionFormat.FULL
    }
}

Read the full file on GitHub · 375 lines

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. 2mo ago First seen · 375 lines · 64 tokens per session scan A a6e2d9c58b00

Subscribe to this mod's changes

kora-testing-junit-kotlin is a skill published in the GitHub repository kora-projects/kora-skills (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 64 tokens to every session and 3,573 once invoked, about $0.0003 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-08-31.

Related

Other skills, from other repositories

swift-testing-pro

Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.

jacklandrin/OnlySwitch · 34 tokens

python-idioms

Modern Python (3.11+) idioms: type annotations, typing Protocols, Pydantic models, asyncio, pytest fixtures, and Ruff/Mypy strict compliance. Use when writing, refactoring, or reviewing Python applications, APIs, or scripts.

irahardianto/awesome-agv · 56 tokens

creating-test

Scaffold a unit test file using the Swift Testing framework. Use when the user asks to create tests, add unit tests, write tests for a manager/presenter/interactor, or scaffold a test file. Mirrors the app's folder structure with Tests naming convention.

SwiftfulThinking/SwiftfulStarterProject · 56 tokens

swift-testing

WHEN writing, running, or diagnosing Swift Testing suites, including migrating XCTest tests to them and a crashing or non-reporting test target under xcodebuild; NOT for authoring XCTest or XCUITest tests; returns macro-driven test patterns, the XCTest boundary, and the correct way to read xcodebuild results.

mintuz/skills · 66 tokens

swift-testing-expert

Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and…

AvdLee/Swift-Testing-Agent-Skill · 73 tokens

guide-swift-testing

Swift Testing patterns — structs over classes, async confirmations, parameterized tests, exit tests, attachments, common agent mistakes. Use when writing, reviewing, or migrating Swift Testing code.

Prisma-Labs-Dev/apple-skills · 41 tokens