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/luanmorenommaciel/kimi-plugin-ccWrote 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/luanmorenommaciel/kimi-plugin-cc/kimi-challenge)<a href="https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/kimi-challenge"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/kimi-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.
<a href="https://agentmods.dev/commands/luanmorenommaciel/kimi-plugin-cc/kimi-challenge"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/kimi-plugin-cc/kimi-challenge.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.00024 | $0.00356 |
| Opus 5 | $0.00012 | $0.00178 |
| Sonnet 5 | $0.00005 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
kimi: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 10d 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.
What it actually says
/kimi:challenge
Steerable adversarial review. Pressure-test assumptions and challenge the chosen approach.
Usage
/kimi:challenge
/kimi:challenge --base main
/kimi:challenge --background look for race conditions and question the caching design
Process
-
Capture diff
Bash("node plugins/kimi/scripts/broker.mjs branch-diff --base <ref>") -
Load challenge prompt template
Read("plugins/kimi/prompts/challenge.md") -
Dispatch to Kimi
- Combine prompt template + diff + optional focus text.
- Use the
explorerole (--role explore). - Invoke via broker:
Bash("node plugins/kimi/scripts/broker.mjs dispatch \ --prompt '<combined>' \ --role explore \ --mode challenge \ [--background]") -
Parse output
- Validate against
schemas/review-output.schema.json. - Render findings grouped by severity.
- Validate against
Output
{
"summary": "string",
"findings": [
{"severity": "warning", "topic": "concurrency", "message": "...", "alternative": "..."}
]
}
Notes
- Read-only. Does not fix code.
- Use before shipping to pressure-test design choices.
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.
- 10d ago First seen · 63 lines · 0 tokens per session scan A b6c2f104448c
kimi:challenge is a command published in the GitHub repository luanmorenommaciel/kimi-plugin-cc (12 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 356 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.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
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.