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/jonapoul/aktual/run-module-testsnpx skills add jonapoul/aktual --skill run-module-testsgit clone --depth 1 https://github.com/jonapoul/aktualWrote 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/jonapoul/aktual/run-module-tests)<a href="https://agentmods.dev/skills/jonapoul/aktual/run-module-tests"><img src="https://agentmods.dev/badge/skills/jonapoul/aktual/run-module-tests.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.00026 | $0.00925 |
| Opus 5 | $0.00013 | $0.00463 |
| Sonnet 5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
run-module-tests 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the correct test task(s) for a Gradle module in this KMP project.
Arguments
$ARGUMENTSshould be the Gradle module path (e.g.,aktual-api,aktual-account:vm,aktual-app:desktop)- If omitted, infer it from the most recently discussed or edited module in conversation context
Step-by-Step Process
1. Determine what test source sets exist
Check which test source set directories exist for the module under src/:
src/commonTest/ -> shared tests (run by both androidHostTest and desktopTest tasks)
src/androidHostTest/ -> Android-specific tests (Robolectric, runs on host JVM)
src/desktopTest/ -> JVM/Desktop-specific tests
src/test/ -> Standard JVM test (JVM-only modules)
Use Glob to check: <module-path>/src/*test*/ and <module-path>/src/*Test*/
The module path on disk uses / separators (e.g., aktual-core/api/src/commonTest), but the Gradle path uses : (e.g., :aktual-api).
2. Determine the module type
Check the module's build.gradle.kts for which convention plugin it uses:
| Plugin | Module Type | Available Test Tasks |
|---|---|---|
aktual.module.kotlin |
KMP | allTests, testAndroidHostTest, desktopTest |
aktual.module.compose |
KMP + Compose | allTests, testAndroidHostTest, desktopTest |
aktual.module.viewmodel |
KMP + Compose + VM | allTests, testAndroidHostTest, desktopTest |
aktual.module.di |
KMP + DI | allTests, testAndroidHostTest, desktopTest |
aktual.module.jvm |
JVM-only | test |
3. Choose the right task
For KMP modules (kotlin/compose/viewmodel/di plugins):
| Source Sets Present | Recommended Task | Why |
|---|---|---|
Only commonTest |
testAndroidHostTest |
commonTest is compiled into both androidHostTest and desktopTest; pick one to avoid running twice. androidHostTest is preferred as it includes Robolectric support. |
Only androidHostTest (with or without commonTest) |
testAndroidHostTest |
Runs commonTest + androidHostTest together |
Only desktopTest (with or without commonTest) |
desktopTest |
Runs commonTest + desktopTest together |
Both androidHostTest and desktopTest |
allTests |
Need both targets to cover all tests |
commonTest + androidHostTest + desktopTest |
allTests |
Need both targets |
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.
- 3d ago First seen · 84 lines · 26 tokens per session scan A fffe2aa583bd
run-module-tests is a skill published in the GitHub repository jonapoul/aktual (33 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 925 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
kotlin-docs
Comprehensive Kotlin 2.4.0 reference covering all language features: variables, basic types, strings, control flow, functions, lambdas, classes, objects, inheritance, interfaces, data classes, sealed classes, generics, collections, sequences, null safety, coroutines (suspend, launch, async, Flow, StateFlow, channels)…
java-kotlin
Java and Kotlin programming patterns.
kotlin-expert
Expert-level Kotlin development, Android, coroutines, and multiplatform.
evergreen
Evergreen CI infrastructure, configuration validation. Use when modifying .evergreen/ config, preparing to submit changes or understanding the Evergreen test matrix.
find-missing-translations
Use when comparing Android strings.xml locale files to find untranslated string resources, missing translation keys, or preparing translation work for a specific language.
android-expert
Android platform patterns for the amethyst/ module. Use when working with (1) Android navigation (Navigation Compose, type-safe routes, bottom nav), (2) runtime permissions (camera, notifications, biometrics), (3) platform APIs (Intent, Context, Activity, ContentResolver), (4) Material3 theming and edge-to-edge UI…