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 skywalkercyt/mp-implement --skill kimi-mp-implementgit clone --depth 1 https://github.com/skywalkercyt/mp-implementWrote 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/skywalkercyt/mp-implement/kimi-mp-implement)<a href="https://agentmods.dev/skills/skywalkercyt/mp-implement/kimi-mp-implement"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/kimi-mp-implement/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/skywalkercyt/mp-implement/kimi-mp-implement"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/kimi-mp-implement.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.00061 | $0.06783 |
| Opus 5.5 | $0.00024 | $0.02713 |
| Sonnet 5.5 | $0.00012 | $0.01357 |
| Haiku 4.5 | $0.00006 | $0.00678 |
Grade A, and why
kimi-mp-implement 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 1mo 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Matt Pocock Implementation Pipeline (Kimi Code edition — AgentSwarm-engined)
Port of mp-implement (v2, Workflow-engined) to the Kimi Code harness. Same methodology, same phases, same HITL checkpoints — the Phase 3 execution engine is rebuilt on Kimi's Agent / AgentSwarm subagents instead of the Claude Code Workflow tool. Running on Claude Code or Codex? Use mp-implement instead — this edition exists because Kimi has no Workflow tool and no schema-enforced structured output.
You are running the full Matt Pocock engineering methodology against a user-provided PRD or design doc: input → canonical PRD → vertical slices → merged code. Stop ONLY at the numbered HITL checkpoints — everything else proceeds AFK.
Relationship to upstream mattpocock/skills
This pipeline is the AFK compression of Matt's human-driven chain (grill-with-docs → to-spec → to-tickets → implement → code-review). Upstream deliberately stays small, composable, and human-driven; this edition keeps the same disciplines but inlines them into prompts and controller steps, and hands user-invoked skills back to the human at HITL checkpoints rather than invoking them mid-run. Synced against upstream v1.1.0 (2026-07).
Input
One argument: a file path (path/to/feature.md), an issue tracker reference (#42, a GitHub/GitLab URL), or .scratch/<feature>/PRD.md. If no argument, ask which PRD/design to operate on, then read it fully.
Persistence (goal-like harness)
You do NOT stop at the end of each phase. You stop only at HITL checkpoints; once a checkpoint resolves, resume without asking. The pipeline runs until all AFK slices are merged or you hit a blocker you cannot resolve. Loops are expected (diagnose → fix → re-verify). Drive forward.
HITL checkpoints at a glance (defined inline at each phase): 1 setup missing · 2 input too sparse · 3 CONTEXT.md sparse · 4 slice approval + merge policy · 5 ambiguity / ADR conflict / test red after 2 honest attempts · 6 load-bearing interface change · 7 stalled agent that won't resume, or cleanup resistance · 8 architecture candidates. Between these: drive forward without asking.
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.
- 1mo ago First seen · 239 lines · 61 tokens per session scan A f9d9c83a0031
kimi-mp-implement is a skill published in the GitHub repository skywalkercyt/mp-implement (2 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 6,783 once invoked, about $0.0002 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
reversi-master
Manage ChatGPT, Codex CLI, and Claude Code accounts and track quota in one place. Use multi-model smart routing with priority and automatic failover. Install AI tools and deploy local LLMs in one click.
Trash Talk
AI becomes provocative and mocks the opponent during gameplay.
game-build
Build a risk-matched whitebox or the approved production game for its target runtime. Turn GAMEDESIGN, and ARTDIRECTION when production begins, into a minimal BUILDBRIEF and a runnable candidate that can be iterated with replayable evidence. Use for prototype the riskiest design question, implement the approved game…
novel-game-analyze
Deconstruct a novel for game adaptation. Compress a raw novel, deconstruction library, or writing project into a SOURCEBIBLE with cited textual evidence, extracting world rules, player verbs, spaces, character will, systems, and visual anchors — without inventing a genre yet. Use for gameable book analysis, analyze a…
novel-to-game
Turn a novel into a fully playable game on the selected target platform. Orchestrates the whole adaptation pipeline — requirements intake, gameable deconstruction, concept selection, world and visual design, target-runtime build, and evidence-based QA — for a novel in any language. Use for novel to game, story to…
game-art-direction
A process for defining the visual and audio direction of a game from its design. It specifies how scenes, characters, interfaces, movement, colour, lighting, materials, sound, and key moments should work together.