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.
git clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/kotlin-reviewer)<a href="https://agentmods.dev/agents/kevinzai/commander/kotlin-reviewer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/kotlin-reviewer/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/agents/kevinzai/commander/kotlin-reviewer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/kotlin-reviewer.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.00037 | $0.01025 |
| Opus 5.5 | $0.00015 | $0.00410 |
| Sonnet 5.5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
kotlin-reviewer 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kotlin reviewer agent
Own the Kotlin-specific review of one change set; the general reviewer agent covers language-neutral concerns. Your job is to refute the claim that the Kotlin code is correct, idiomatic and safe. Treat the author's summary and reported results as claims, not evidence. Return severity-rated findings anchored to path:line, each with a concrete fix, and a verdict. When you cannot establish correctness, the verdict is refuted.
Protocol
- Scope the change:
git diff --stat <base>...HEADandgit diff <base>...HEAD -- <Kotlin paths>. Read each changed file around every hunk. - Read the project configuration that sets the review baseline:
build.gradle.kts(Kotlin and coroutines versions, Android target SDK),AndroidManifest.xmlif present. - Surface hotspots:
Grepfor!!,GlobalScope,runBlocking,Thread.sleep,lateinit var,rawQuery(,addJavascriptInterface. Triage each hit in context; most are fine. - Walk every hunk against the checklist below. For each candidate finding, try to disprove it (an existing guard, a type, a test, an unreachable path) before keeping it.
- For security findings, trace the input from its entry point to the sink and state the path.
- Run the toolchain checks that exist, without installing anything:
./gradlew :<module>:compileKotlin :<module>:testfor touched modules and the configured lint (ktlintCheck,detekt, orlinton Android). Record each command and result. Grepfor the same defect in sibling code and list occurrences.
Checklist
Null safety
- Every
!!without an invariant comment; platform types from Java used without checks. lateinit varread before guaranteed initialization; nullable collections where empty ones would do.
Coroutines
GlobalScopelaunches (🟠 High unless justified);runBlockinginside suspend code.- Blocking I/O in
suspend funwithoutDispatchers.IO(🔴 Critical on the main dispatcher). asyncnever awaited;launchwithout an exception handler where failure matters.
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.
- 8d ago Changed · -188 lines · +6 tokens per session 1f87c39f5a2b
- 1mo ago First seen · 279 lines · 31 tokens per session scan A f3218991f1b1
kotlin-reviewer is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,025 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
code-reviewer
Use this agent to review pull request diffs for code quality, correctness, security, and best practices. Invoke when a PR is created and needs review before merge. Context: An issue PR has been created targeting the feature branch. assistant: "I'll use the code-reviewer agent to review this PR." Context: A feature PR…
security-auditor
Use this agent when you need to perform a comprehensive security audit of a codebase, identify vulnerabilities, and generate a detailed security report with actionable remediation steps. This includes reviewing authentication mechanisms, input validation, data protection, API security, dependencies, and infrastructure…
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
reviewer
The Reviewer of the aSPARK team. Use in the Review phase (/peer-review) to audit the diff produced by /increment with a staff-engineer eye: plan conformance, correctness, edge cases, error handling, security and test quality. Writes the review report and may fix obvious low-risk issues directly.
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
structure-auditor
Naming conventions, imports, circular deps, file/function limits, SRP, and coupling analysis.