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 Cratis/AI --skill cratis-arc-testing-kotlingit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/cratis-arc-testing-kotlin)<a href="https://agentmods.dev/skills/cratis/ai/cratis-arc-testing-kotlin"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-arc-testing-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/cratis/ai/cratis-arc-testing-kotlin"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-arc-testing-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.00086 | $0.01466 |
| Opus 5.5 | $0.00034 | $0.00586 |
| Sonnet 5.5 | $0.00017 | $0.00293 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
cratis-arc-testing-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 7d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specify Arc behavior on the JVM
Use generated artifacts through the real pipelines, not hand-written handlers
that bypass KSP wiring. arc-testing needs neither Spring Boot nor Docker.
This is test support, not an alternative production host.
Verified product sources
Source: Arc.Kotlin: Testing/src/main/kotlin/io/cratis/arc/testing
(CommandScenario, QueryScenario, ObservableQueryScenario, result assertions),
Integrations/Chronicle/ChronicleCommandScenario.kt, and
Documentation/guides/testing.mdx. Add
testImplementation("io.cratis:arc-testing:<version>"); align it with the runtime,
plugin and KSP version.
Choose the pipeline
| Behavior | Scenario |
|---|---|
| Execute or validate a command | CommandScenario(module, CommandType::class.java) |
| One-shot query | QueryScenario<T> selected by FullyQualifiedQueryName |
| Streaming query | ObservableQueryScenario<T> with bounded collect(maximumEmissions, timeoutMillis) |
Application specs select a generated ArcArtifactModule. Manual
CommandHandler/QueryPerformer constructors are for framework tests.
Arrange services, validators, authorization policies, filters, principal,
tenant and correlation id on the scenario before executing it.
Illustrative excerpt: module is the generated module; CreateTask and its
TaskRepository/TaskCreated types are supplied by the application.
// Copyright (c) Cratis. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
import io.cratis.arc.testing.CommandScenario
val result = CommandScenario(module, CreateTask::class.java)
.addService(TaskRepository::class.java, repository)
.execute(CreateTask("Try Arc"))
result.shouldSucceed().shouldHaveResponse(TaskCreated::class.java)
Command and one-shot query scenarios perform JSON round trips by default, including the module's registered derived types. Keep them enabled to exercise wire behavior. Disable them only for a deliberate pure/in-process assertion; serialization failures propagate to the test, not a successful result. Observable scenarios do not perform opening-argument or result-data round trips.
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.
- 7d ago Changed 659f8a2c13c3
- 8d ago First seen · 132 lines · 86 tokens per session scan A 8e303f376661
cratis-arc-testing-kotlin is a skill published in the GitHub repository Cratis/AI (4 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 1,466 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-10-13.
Other skills, from other repositories
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices. Use when writing Kotlin tests with Kotest or MockK, or testing coroutines and checking coverage.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.