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/chianw/c31/kimiimnpx skills add ChianW/C31 --skill kimiimgit clone --depth 1 https://github.com/ChianW/C31Wrote 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/chianw/c31/kimiim)<a href="https://agentmods.dev/skills/chianw/c31/kimiim"><img src="https://agentmods.dev/badge/skills/chianw/c31/kimiim.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.00082 | $0.03187 |
| Opus 5 | $0.00041 | $0.01594 |
| Sonnet 5 | $0.00016 | $0.00637 |
| Haiku 4.5 | $0.00008 | $0.00319 |
Grade A, and why
kimiim-cli 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.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multilingual Triggers
| Language | Trigger phrases |
|---|---|
| EN | kimiim |
| ZH | kimi记忆, 导入记忆 |
| JA | Kimi記憶 |
Output language: Respond automatically in the user's conversation language.
kimiim-cli
Core Model
- A group chat is a long-running multi-agent workspace. There may be users, a Coordinator, and multiple agents working in parallel.
- A thread is still part of the same group, but it has its own isolated chat history. Reply in the same chat where the work is happening.
- Follow the Coordinator's instructions, but do not be passive. Good group work means reading the room, interacting with others, and moving the task forward.
- Mention people with the exact short-id form
<@Member_Name|Member_ShortID>, if you don't mention the agents, they won't receive your message. list-membersis for room awareness, not for opening conversations with everyone you discover there. Seeing a worker in the roster does not by itself authorize you to message them.- Group chat memory is workspace-scoped, not long-term memory. Store required group memories under
.openclaw/workspace/kimi-group-chat/{group-name}/memory.md. - Store files produced for group tasks under
.openclaw/workspace/kimi-group-chat/{group-name}/unless the task explicitly requires a different location.
Mandatory Startup Workflow
When you receive a new message from a group or thread, follow this order before starting the task:
- Run
get-group <group_id>first and read the Group Rules and group information. - After you know
{group-name}, read the group memory under.openclaw/workspace/kimi-group-chat/{group-name}/memory.md. - If this is a new Session, do that memory read immediately after
get-group, before any task work. - Run
list-members <group_id>to see which agents and users are in the room，including their Member_Name and Member_ShortID. - Run
list-messages <chat_id>to inspect recent context before you speak or act. - Only after those reads should you start the task, reply, or ask for clarification.
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 · 269 lines · 82 tokens per session scan A dc0dbab7daa6
kimiim-cli is a skill published in the GitHub repository ChianW/C31 (1 stars, last pushed 10d ago), licensed MIT. It adds 82 tokens to every session and 3,187 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-31.
Other skills, from other repositories
agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
oia-manifest
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
create-harness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
example-harness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…