Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add XinyuQu/llm-review/plugin install llm-reviewWrote 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/commands/xinyuqu/llm-review/kimi)<a href="https://agentmods.dev/commands/xinyuqu/llm-review/kimi"><img src="https://agentmods.dev/badge/commands/xinyuqu/llm-review/kimi/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/commands/xinyuqu/llm-review/kimi"><img src="https://agentmods.dev/badge/commands/xinyuqu/llm-review/kimi.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.00016 | $0.00704 |
| Opus 5 | $0.00008 | $0.00352 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
kimi 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get an adversarial code review from Kimi of the current changes.
Raw slash-command arguments: $ARGUMENTS
Parse $ARGUMENTS into the engine command (build as separate args, never splice
the raw string into a shell line):
- first bare word not starting with
-→ base git ref, pass as--base <ref> --staged→ review staged changes only--diff-only→ restrict the reviewer to the diff (don't let it read other repo files), pass as--diff-only--wait→ execution mode (don't pass to engine; foreground)--background→ execution mode (don't pass to engine; background)
Execution mode
Reviews against large diffs legitimately take several minutes. Default to background so the Claude Code session is not blocked.
- If
$ARGUMENTScontains--wait: foreground, skip the question. - If
$ARGUMENTScontains--background: background, skip the question. - Otherwise, estimate diff size first, then ask:
- Run
git diff --shortstat(orgit diff --shortstat --stagedif--staged, orgit diff --shortstat <base>...HEADif a base was given). - Tiny (≤2 files changed and no large directory rewrite) → recommend wait.
- Otherwise → recommend background.
- Call
AskUserQuestiononce with two options, recommended first and suffixed with(Recommended):Wait for resultsRun in background
- Run
Foreground path
Run synchronously:
node "${CLAUDE_PLUGIN_ROOT}/scripts/llm-review.mjs" review --provider kimi [--base <ref>] [--staged] [--diff-only]
Then present Kimi's review to the user verbatim — do not soften, summarize,
or re-rank its findings. It is an independent second opinion; preserve its
severities and verdict. If the command errored (missing API key, no changes,
etc.), relay the error and point the user to /llm-review:setup.
Background path
Launch the review with Bash(run_in_background: true):
node "${CLAUDE_PLUGIN_ROOT}/scripts/llm-review.mjs" review --provider kimi --background [--base <ref>] [--staged] [--diff-only]
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 · 65 lines · 16 tokens per session scan A d1ee8b54ce4d
kimi is a command published in the GitHub repository XinyuQu/llm-review (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 704 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-08-31.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.