A read-only review command that tries to break the design behind your current code changes. It checks the proposed approach for hidden risks and questionable trade-offs.

Use it to review a git diff, identify failure modes, compare alternative designs, and receive findings grouped by severity and topic.

It helps reveal problems that ordinary code review may miss, such as race conditions, data loss, weak rollback plans, or untested assumptions.

challenge — Command for Claude Code by luanmorenommaciel

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.

Clone the repo

git clone --depth 1 https://github.com/luanmorenommaciel/kimi-plugin-cc

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/challenge/github.svg)](https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/challenge)

Your own site

<a href="https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/challenge"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/challenge/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/challenge"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/challenge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 226 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.00226
Opus 5.5	$0.00006	$0.00090
Sonnet 5.5	$0.00003	$0.00045
Haiku 4.5	$0.00001	$0.00023

Measured 2mo ago against content hash 63b5374b7c42, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

plugins/kimi-code/commands/challenge.md · 32 lines

What it actually says

You are a skeptical, adversarial reviewer. Pressure-test the implementation of the current changes (git diff, or git diff <ref>...HEAD if a ref is mentioned below).

Focus: $ARGUMENTS

Question whether the approach is the simplest safe choice.
Identify hidden assumptions and failure modes.
Look for race conditions, data loss risks, rollback concerns.
Challenge trade-offs: what was gained vs. what was sacrificed?
Suggest alternative approaches that were not considered.

Return ONLY a JSON object:

{
  "summary": "One-line verdict on overall design safety",
  "findings": [
    {
      "severity": "info|warning|critical",
      "topic": "e.g., concurrency, data model, error handling",
      "message": "What is questionable",
      "alternative": "What could have been done instead"
    }
  ]
}

Be constructive but unsparing. Do not fix code — only identify problems and suggest directions. Read-only.

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.

2mo ago First seen · 32 lines · 14 tokens per session scan A 63b5374b7c42

Subscribe to this mod's changes

challenge is a command published in the GitHub repository luanmorenommaciel/kimi-plugin-cc (14 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 226 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-08-31.

Code review

challenge next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
challengeluanmorenommaciel/kimi-plugin-cc	Command	14	3mo ago	MIT	A	14	Claude Code
diff-reviewcoco-research/coco	Command	785	yesterday	Apache-2.0	A	11	Claude Code
review-branchdamusix/atomic-claude	Command	115	5d ago	MIT	A	35	Claude Code
refactorRchGrav/claudebox	Command	1.2k	1mo ago	MIT	A	9	Claude Code
spec-trace-requirementsrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
initazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	16	Claude Code