challenge

A command that asks Kimi to review work by questioning its assumptions and suggesting safer alternatives.

In plain words
What is it for?
Use it to challenge a change, focus the review on a specific concern, or compare the current work with another branch or commit.
Why use it?
It provides a second, adversarial review of the working tree or a chosen branch or commit, helping expose risks the main review may miss.

Command

Install

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.

agentmods
npx agentmods add commands/linxule/kimi-plugin-cc/challenge
Clone the repo
git clone --depth 1 https://github.com/linxule/kimi-plugin-cc
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 183 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00183
Opus 5 $0.00008 $0.00092
Sonnet 5 $0.00003 $0.00037
Haiku 4.5 $0.00002 $0.00018

Measured 2d ago against content hash 7131e086e84c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

challenge 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 2d 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.

commands/challenge.md · 20 lines

What it actually says

Run the companion with any user-supplied flags appended after task challenge:

${CLAUDE_PLUGIN_ROOT}/scripts/companion.sh task challenge <args>

Supported flags:

  • --base <ref> — challenge against a branch/commit diff instead of the working tree
  • -m, --model <name>
  • trailing text — adversarial focus or framing to steer the challenge

Kimi's extended reasoning is always on for challenge. Budget is 30 min so adversarial review has time to dig. Challenge runs foreground-synchronously; it does not support --background or --wait.

Return the companion stdout verbatim.

Changes

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.

  1. 2d ago First seen · 20 lines · 16 tokens per session scan A 7131e086e84c

Subscribe to this mod's changes

challenge is a command published in the GitHub repository linxule/kimi-plugin-cc (37 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 183 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-30.