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 mp-implement-issuegit 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/mp-implement-issue)<a href="https://agentmods.dev/skills/skywalkercyt/mp-implement/mp-implement-issue"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/mp-implement-issue/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/mp-implement-issue"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/mp-implement-issue.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.00066 | $0.02892 |
| Opus 5.5 | $0.00026 | $0.01157 |
| Sonnet 5.5 | $0.00013 | $0.00578 |
| Haiku 4.5 | $0.00007 | $0.00289 |
Grade A, and why
mp-implement-issue scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Build a feedback loop** (THE skill — failing test, curl script, headless browser, replay harness — whichever reaches the bug fastest). Spend disproportionate effort here. Done when you can name ONE command — red-cap How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Matt Pocock — Single Issue Implementation
Pick up ONE AFK-labeled issue and drive it to a merged PR. Lighter than /mp-implement (no decomposition phase) — assumes the slice already exists.
Input
The user invokes with:
- An issue reference (
#42, GitHub URL, GitLab URL, or.scratch/<feature>/<slice>.mdfor local-markdown trackers) - Or no argument → query the configured tracker for the oldest unblocked
ready-for-agentissue and ask the user to confirm before starting.
Persistence
Drive until the issue is merged (or hits a HITL checkpoint below). Do not stop after each step.
Process
1. Read the slice fully
Fetch the issue body, all comments, prior triage notes, and the agent brief (per docs/agents/issue-tracker.md). Read the parent PRD referenced in the "Parent" section.
If docs/agents/triage-labels.md indicates the issue is NOT ready-for-agent, stop and tell the user — refuse to pick it up without explicit override.
2. Verify context
Read CONTEXT.md (or CONTEXT-MAP.md → relevant per-context file) and any ADRs in the area. Note any constraint that affects your approach. Use this vocabulary throughout. If you're unfamiliar with this code area, map the relevant modules and callers using the domain glossary first — context matters more than speed.
3. Worktree + branch + clean baseline
Apply /using-git-worktrees: detect existing isolation, then set up an isolated worktree (or work in place if the user declines or the harness already isolates). Inside it, create a feature branch named after the slice title (kebab-case).
/using-git-worktrees also auto-runs project setup and verifies a clean test baseline — never start from a broken baseline. If tests fail on the clean checkout, stop and report before writing any code.
4. Prototype if a key question is open
If a state-model, data-model, or UI question is genuinely unresolved after reading the slice + PRD + CONTEXT, apply /prototype discipline: build the throwaway, answer the question, fold the decision back. Capture the answer in the slice (as a comment) or in an ADR if it meets the three criteria.
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 · 164 lines · 66 tokens per session scan A f92f131f03dd
mp-implement-issue is a skill published in the GitHub repository skywalkercyt/mp-implement (2 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 2,892 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…