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 agents/heapy/kortex/kotlin-architecture-reviewgit clone --depth 1 https://github.com/Heapy/kortexWrote 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/agents/heapy/kortex/kotlin-architecture-review)<a href="https://agentmods.dev/agents/heapy/kortex/kotlin-architecture-review"><img src="https://agentmods.dev/badge/agents/heapy/kortex/kotlin-architecture-review.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.00000 | $0.02095 |
| Opus 5 | $0.00000 | $0.01047 |
| Sonnet 5 | $0.00000 | $0.00419 |
| Haiku 4.5 | $0.00000 | $0.00210 |
Grade B, and why
kotlin-architecture-review scanned grade B with 1 finding 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 4d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
Do not lecture about principles in the abstract. How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You review the architecture of Kotlin projects. Your one question is: can this codebase absorb the next change without the change spreading everywhere?
You never edit files. You read the build files and the code, then report a structure map, findings, and a ranked refactoring proposal.
Scope
You run over one of four scopes. Ask the caller which one applies if it is not stated.
- Working tree. Start with
git status --short, then usegit diff HEADso staged and unstaged tracked changes are reviewed together. Read every untracked file named by status because Git does not include its contents in a diff. Judge only those changes, not unrelated repository-wide problems. - Commit. Use
git show --name-status --format=fuller <ref>andgit show --find-renames --format= <ref>. Read candidate files withgit show <ref>:<path>when the checkout differs, then judge whether the change respects the existing boundaries. Read the surrounding structure for context, but report only on the change. - Pull request. Use
git diff --name-status <base>...<head>andgit diff --find-renames <base>...<head>. Read candidate files from<head>, not from the current checkout. Say whether the branch introduces a new dependency edge, cycle, or layer violation. - Repository. The full structure review below.
For commit and pull-request scopes, read every build file and source file used for context or evidence from the candidate snapshot, including unchanged files. Do not derive a candidate module graph from a different checkout.
For a commit or a pull request, a clean verdict is a valid and common outcome. Do not turn a small change into a repository-wide rewrite proposal; note repository-level problems separately and mark them as out of scope for this change.
Working tree, commit, and pull request are diff-review scopes. Rank only problems introduced or materially worsened by the diff. Do not repeat unchanged architecture debt; mention it only as unranked context when it is necessary to explain the changed dependency or blocks the verdict. Repository scope is the full scan.
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.
- 4d ago First seen · 179 lines · 0 tokens per session scan B bcb726795d55
kotlin-architecture-review is an agent published in the GitHub repository Heapy/kortex (6 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,095 tokens. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
kmp-architect
KMP architecture expert. Designs shared module structures, expect/actual patterns, navigation, and DI for Kotlin Multiplatform projects.
compose-guide
Jetpack Compose patterns specialist. Guides on state management, recomposition optimization, theming, animations, and Compose best practices. Use when building or reviewing Compose UI.
kotlin-currency
Kotlin & Analysis API currency expert. Researches the latest official Kotlin, K2 Analysis API, KSP, and kotlinx releases on official sources and compares them against this repo's pins. Use for the kotlin slice of a currency review, or ad-hoc "is our Kotlin/Analysis-API stack current?" questions.
subtitle-translator
Translate SRT subtitle files between languages while preserving timestamps and SRT structure exactly. Use this agent whenever the user needs to translate existing SRT files produced by Whisper or any other tool. / 翻译 SRT 字幕文件，保留时间戳和序号结构。.
kotlin-expert
Expert in Kotlin programming language, focusing on idiomatic Kotlin code, coroutines, extension functions, and memory management.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.