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-blackboxWrote 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-blackbox)<a href="https://agentmods.dev/skills/kora-projects/kora-skills/kora-testing-blackbox"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-testing-blackbox/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-blackbox"><img src="https://agentmods.dev/badge/skills/kora-projects/kora-skills/kora-testing-blackbox.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.00066 | $0.02769 |
| Opus 5 | $0.00033 | $0.01385 |
| Sonnet 5 | $0.00013 | $0.00554 |
| Haiku 4.5 | $0.00007 | $0.00277 |
Grade A, and why
kora-testing-blackbox 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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kora Testing Black-Box — E2E via HTTP API
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.
Black-box tests run the packaged application (the distTar/installDist artifact) inside a Docker container and exercise it only through the public HTTP API. The test never injects into or modifies the Kora graph — it runs the same code that ships.
Kora builds its dependency graph at compile time, so startup is fast enough to make black-box tests a primary confidence source, not just a smoke suite. They catch what narrower tests miss: routing, @Json (de)serialization, @Valid validation, config loading, migrations, and probes all exercised together.
Kora ships no Testcontainers wrapper. Use the standard
org.testcontainers:*API directly. For in-process tests with@KoraAppTest/@TestComponent, use thekora-testing-junit-java/kora-testing-junit-kotlinskills instead.
Contents
- Quick Start — deps, Dockerfile, AppContainer, first test
- What's in references/ and assets/
- When to use vs NOT
- Core patterns
- Common pitfalls
Quick Start
Pin all Kora artifacts through the kora-parent BOM; never version ru.tinkoff.kora:* deps individually. The example repo uses BOM 1.2.19.
1. Dependencies (build.gradle)
dependencies {
koraBom platform("ru.tinkoff.kora:kora-parent:1.2.19")
// Annotation processor is mandatory for any Kora module to generate code.
annotationProcessor "ru.tinkoff.kora:annotation-processors"
testAnnotationProcessor "ru.tinkoff.kora:annotation-processors"
testImplementation platform("org.junit:junit-bom:5.14.3")
testImplementation "org.junit.jupiter:junit-jupiter"
testImplementation project(":my-service-app") // the packaged app module
testImplementation "ru.tinkoff.kora:test-junit5"
testImplementation "org.json:json:20231013"
testImplementation "org.testcontainers:junit-jupiter:1.21.4"
testImplementation "org.testcontainers:testcontainers:1.21.4"
testImplementation "org.testcontainers:postgresql:1.21.4"
}
test {
// Build the distribution archive the Dockerfile copies, before tests run.
dependsOn ":my-service-app:distTar"
inputs.file("../my-service-app/Dockerfile")
inputs.file("../my-service-app/build/distributions/application.tar")
useJUnitPlatform()
}
What ships with it
12 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/BlackBoxTest-RestAssured.java.template 6.2 KB
- assets/BlackBoxTest-RestAssured.kt.template 6.1 KB
- assets/BlackBoxTest.java.template 6.6 KB
- assets/BlackBoxTest.kt.template 6.6 KB
- assets/Dockerfile.self-build-kotlin.template 1.8 KB
- assets/Dockerfile.self-build.template 1.8 KB
- assets/Dockerfile.template 892 B
- evals/evals.json 7.2 KB
- references/blackbox-integration-reference.md 18 KB
- references/docker-compose-reference.md 12 KB
- references/docker-reference.md 9.5 KB
- references/testcontainers-reference.md 10 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.
- 9d ago First seen · 260 lines · 66 tokens per session scan A 36abb83d2044
kora-testing-blackbox is a skill published in the GitHub repository kora-projects/kora-skills (1 stars, last pushed 8d ago), licensed Apache-2.0. It adds 66 tokens to every session and 2,769 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
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
dogfood
Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
horse-integration-tests
Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…