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 agentmods add skills/linxule/kimi-plugin-cc/kimi-setupnpx skills add linxule/kimi-plugin-cc --skill kimi-setupgit 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-setup)<a href="https://agentmods.dev/skills/linxule/kimi-plugin-cc/kimi-setup"><img src="https://agentmods.dev/badge/skills/linxule/kimi-plugin-cc/kimi-setup.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.00512 |
| Opus 5 | $0.00044 | $0.00256 |
| Sonnet 5 | $0.00017 | $0.00102 |
| Haiku 4.5 | $0.00009 | $0.00051 |
Grade A, and why
kimi-setup 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 4d 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 Setup
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" setup <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: [--check | --uninstall [--all] | --enable-review-gate | --disable-review-gate]
Handling
- Run setup from the user's workspace so the companion records the intended workspace cwd.
- Use
--checkfor read-only verification and--uninstallonly when explicitly requested.--uninstallremoves only this host's block;--uninstall --allremoves every host's block from the shared config. - Setup validates the complete shared TOML and every configured hook under a serialized lock. If it reports invalid foreign config, surface that failure; do not bypass it or claim the managed block is safe in isolation.
- Report setup stdout verbatim because it contains hook and probe status.
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.
- 4d ago First seen · 28 lines · 87 tokens per session scan A 15459dfc56ef
kimi-setup is a skill published in the GitHub repository linxule/kimi-plugin-cc (37 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 512 once invoked, about $0.0004 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
kimi-cli-runtime
Internal helper contract for calling the kimi-companion runtime from Claude Code.
kimi-k2-prompting
How to write effective prompts for Kimi K2.7 when delegating.
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.