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.
npx skills add linxule/kimi-plugin-cc --skill kimi-challengegit clone --depth 1 https://github.com/linxule/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/skills/linxule/kimi-plugin-cc/kimi-challenge)<a href="https://agentmods.dev/skills/linxule/kimi-plugin-cc/kimi-challenge"><img src="https://agentmods.dev/badge/skills/linxule/kimi-plugin-cc/kimi-challenge.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.00423 |
| Opus 5 | $0.00023 | $0.00211 |
| Sonnet 5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
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 7d 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
Forward this request to the local kimi-code companion runtime by shell. Do not use MCP for this skill.
Invocation
- Resolve the plugin root: prefer
$PLUGIN_ROOTif the host sets it; otherwise use the directory that CONTAINS theskills/directory (i.e. two levels up from thisSKILL.md). - Sanity check:
<plugin-root>/scripts/companion.shmust exist — it is the bundled entrypoint that resolves Node and runs the compiled runtime from<plugin-root>/dist/. - Launch the shell command from the user's current workspace directory so
scripts/companion.shcaptures the intended workspace cwd. - Run:
PLUGIN_ROOT="<plugin-root>" "<plugin-root>/scripts/companion.sh" task challenge <args> - If the plugin host provides
PLUGIN_DATAinstead ofCLAUDE_PLUGIN_DATA, the shell wrapper exports the Claude-compatible alias for the runtime. If neither is set, the wrapper uses a Codex data directory under$CODEX_HOME/plugins/data/kimi-marketplace-kimi,~/.codex/plugins/data/kimi-marketplace-kimi, or/tmp/kimi-plugin-cc-codex-data/kimi-marketplace-kimiin a fully sanitized environment.
Arguments
Pass through: [--base <ref>] [-m <model>] [extra prose]
Handling
- Preserve the user's adversarial framing as trailing focus text.
- Do not pass background/wait flags; the runtime rejects them for challenge.
- If the companion reports CHALLENGE_HOOK_NOT_INSTALLED, tell the user to run Claude Code /kimi:setup or Codex $kimi-setup, then retry; do not suggest the skip env.
- Return companion stdout verbatim without softening the challenge framing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 28 lines · 45 tokens per session scan A 1f7fb67481f5
kimi-challenge is a skill published in the GitHub repository linxule/kimi-plugin-cc (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 423 once invoked, about $0.0002 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.
Other skills, from other repositories
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
code-review
The depth half of a review - the dimensions a diff is read against (correctness, boundaries, concurrency, failure paths, secrets, data access, structure, test quality) and the rule that a finding is refuted before it is reported. The verdict stays with the reviewer agent. Use when reviewing a diff or a pull request…
deslop
The optimization pass, defined - delete before you add, one smell class per pass, behaviour pinned by a test that ran BEFORE the edit. Lints a SKILL.md and prose by the same instinct. Use for the per-story optimization pass or when code has grown noisy without growing capable.
loop-test
A local experiment for designing repeating checks with Claude Code’s loop command. It covers both fixed intervals and checks that schedule themselves again after each run.
take-task
A workflow for claiming a tracker task and preparing the development branch for it. It verifies the task, marks it as in progress, checks for uncommitted changes, and handles branch setup according to the task state.
goal-plan-clean
A guide for creating a reusable plan-review loop. It repeatedly checks a plan, fixes blocking issues and suggestions, and stops after approval or a small number of review rounds.