Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ImL1s/agent-cli-skillsnpx agentmods add skills/iml1s/agent-cli-skills/kimi-cli-agentWrote 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/iml1s/agent-cli-skills/kimi-cli-agent)<a href="https://agentmods.dev/skills/iml1s/agent-cli-skills/kimi-cli-agent"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/kimi-cli-agent/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/skills/iml1s/agent-cli-skills/kimi-cli-agent"><img src="https://agentmods.dev/badge/skills/iml1s/agent-cli-skills/kimi-cli-agent.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.00089 | $0.00557 |
| Opus 5.5 | $0.00036 | $0.00223 |
| Sonnet 5.5 | $0.00018 | $0.00111 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
kimi-cli-agent 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.
What it actually says
Kimi Code CLI (kimi) Executor
When to use
- User wants kimi / Kimi Code as the coding agent
- Need Kimi agent Markdown profiles or built-in sub-agents from an orchestrator
Wrapper
./kimi-exec.sh -C /path/to/repo -t 1800s "Implement phase A. NO git."
./kimi-exec.sh -r -o json "Review this design; do not edit."
./kimi-exec.sh --agent-file ./agents/reviewer.md -f /tmp/bundle.txt
./kimi-exec.sh -T -C /path/to/repo "Delegate via sub-agents"
Flags: -m (default kimi-code/k3) · -t · -C · -o text|json|stream-json · -f · -r ·
-T · --agent · --agent-file · --skills-dir · --add-dir · --no-git · -- passthrough.
No PTY needed. Wrapper always runs --output-format stream-json internally and cleans to text/json.
-C is absolutized; --add-dir uses the physical workspace path.
Headless permission model
kimi -pauto-approves tools (it is an executor by default)- Interactive
--yolo/--auto/--plancannot be combined with-p -ris a soft read-only prompt guard — for hard isolation use a throwaway worktree
Native multi-agent
Custom agents as Markdown (--agent / --agent-file); built-in sub-agents; discovery from
project/user agent dirs. No dedicated /teamwork slash — use -T + agent profiles.
Quota
On 403 usage limit: do not retry-loop. Mark the seat BLOCKED and continue with other CLIs.
Discipline
Exit code untrusted. Orchestrator owns git. Prefer -f for long bundles.
What ships with it
4 files 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.
- 2mo ago First seen · 50 lines · 89 tokens per session scan A 0f5b8b52a973
kimi-cli-agent is a skill published in the GitHub repository ImL1s/agent-cli-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 557 once invoked, about $0.0004 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.
Other skills, from other repositories
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
financial-analysis
Financial figures done carefully: periods and fiscal calendars, units and currencies, reconciliation, magnitude sanity checks, sourced assumptions. Use for statements, budgets, pricing, and diligence numbers.