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 deepseek-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/deepseek-mp-implement)<a href="https://agentmods.dev/skills/skywalkercyt/mp-implement/deepseek-mp-implement"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/deepseek-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/deepseek-mp-implement"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/deepseek-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.00111 | $0.02451 |
| Opus 5.5 | $0.00044 | $0.00980 |
| Sonnet 5.5 | $0.00022 | $0.00490 |
| Haiku 4.5 | $0.00011 | $0.00245 |
Grade A, and why
deepseek-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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deepseek MP Implement
Matt Pocock methodology, but Phase 3 (implementation + quality review) runs on Codex instead of Claude Code subagents. This session stays lean — you plan, coordinate, and do spec-compliance verification. Codex does the heavy lifting.
Why this variant
| Phase | mp-implement (original) | deepseek-mp-implement |
|---|---|---|
| Plan (0-2) | This session | This session (unchanged) |
| Implement | Claude Code subagent in worktree | /codex:rescue → Codex mp-implement-issue |
| Code-quality review | Claude Code subagent | /codex:adversarial-review --wait |
| Spec-compliance review | Claude Code subagent | Claude Code subagent (unchanged — needs issue body) |
| Hygiene (4) | This session | This session (unchanged) |
Relationship to upstream mattpocock/skills
This is the Codex-engine variant: the AFK compression of Matt's human-driven chain (grill-with-docs → to-spec → to-tickets → implement → code-review) with Phase 3 delegated to Codex. Upstream deliberately stays small, composable, and human-driven; this fork trades that for AFK throughput. Synced against upstream v1.1.0 (2026-07).
Terminology: local "PRD"/"slices" ≈ upstream "spec"/"tickets".
Input
Same as mp-implement: a file path, an issue tracker reference, or a PRD description. If no argument, ask the user.
Pipeline
[Phase 0] Setup verification ──→ HITL if repo not configured
[Phase 0.5] Canonicalize input → PRD ──→ HITL only if too sparse
[Phase 1] Domain alignment ──→ HITL if CONTEXT.md sparse
[Phase 2] Decomposition ──→ HITL on slice approval
[Phase 3] Per-slice: Codex loop ──→ AFK until all slices done
│
├── dispatch Codex via /codex:rescue (mp-implement-issue + issue URL)
├── /codex:adversarial-review --wait (code quality, before commit)
├── commit + push + PR (controller does this)
├── Claude subagent spec-compliance review
└── merge → next slice
[Phase 4] Closing hygiene ──→ AFK
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 · 203 lines · 111 tokens per session scan A 6273e0931e4f
deepseek-mp-implement is a skill published in the GitHub repository skywalkercyt/mp-implement (2 stars, last pushed 2mo ago), licensed MIT. It adds 111 tokens to every session and 2,451 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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…