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.
git clone --depth 1 https://github.com/kora-projects/kora-skillsnpx agentmods add skills/kora-projects/kora-skills/kora-testing-junit-kotlinWrote 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/kora-projects/kora-skills/kora-testing-junit-kotlin)<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.
<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>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.00064 | $0.03573 |
| Opus 5 | $0.00032 | $0.01786 |
| Sonnet 5 | $0.00013 | $0.00715 |
| Haiku 4.5 | $0.00006 | $0.00357 |
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 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.
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
TestApplicationsubmodule 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
}
}
What ships with it
11 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.
- assets/ComponentTest.kt.template 1.2 KB
- assets/IntegrationTest.kt.template 2.4 KB
- assets/IntegrationTestWithPostgres.kt.template 3.4 KB
- assets/TestApplication.kt.template 1.2 KB
- evals/evals.json 5.9 KB
- references/coroutines-testing-reference.md 4.7 KB
- references/junit5-extension-reference.md 5.6 KB
- references/korapptest-kotlin-reference.md 4.8 KB
- references/mockito-reference.md 4.3 KB
- references/mockk-reference.md 5.4 KB
- references/testcontainers-kotlin-reference.md 4.2 KB
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 · 375 lines · 64 tokens per session scan A a6e2d9c58b00
kora-testing-junit-kotlin is a skill published in the GitHub repository kora-projects/kora-skills (1 stars, last pushed 10d 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. 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
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.
swift
Swift development: concurrency patterns, async/await, actors, testing with XCTest and Swift Testing framework.
modernize-tests
Modernize test suites to use modern Swift Testing features or migrate from XCTest.
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…
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.
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.