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/skywalkercyt/mp-implement/deepseek-mp-implementnpx skills add skywalkercyt/mp-implement --skill deepseek-mp-implementgit clone --depth 1 https://github.com/skywalkercyt/mp-implementWhat 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.00111 | $0.02451 |
| Opus 5 | $0.00056 | $0.01226 |
| Sonnet 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 2d 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.
- 2d 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 29d ago), licensed MIT. It adds 111 tokens to every session and 2,451 once invoked, about $0.0006 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
nunit-code-style
Use when writing or modifying C# method bodies, type declarations, or non-trivial logic in NUnit source. Covers NUnit's taste-and-judgment conventions — exception construction, simplification, naming intent, StringComparison, non-null check form, and var usage — that aren't already caught at build time.
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
software-test-execution
Run scoped tests for a TDD slice, determine the appropriate test framework and command, and report structured pass/fail results. Use when tests need to be executed after writing, implementing, or refactoring code. Reads test metadata, discovers the test framework if needed, executes the scoped test command, parses…
nunit-api-design
Use when adding or modifying public API surface in NUnit — new or changed constraints, attributes, assertions, helpers, or any type/member visibility change. Covers the conventions NUnit maintainers enforce for types that ship to consumers of the framework.
nw-at-completeness-check
Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.
nw-ab-critique-dimensions
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation.