agentmods.dev

mpga-develop

mpga-develop is a skill for Claude Code from benrben/MPGA. It costs 29 tokens per session (1,313 once invoked), scanned A, original, MIT.

A guided TDD workflow, where test-driven development means writing a failing test before the code that makes it pass. It repeats red, green, and review phases for each task.

In plain words
What is it for?
Use it to claim tasks, load their requirements, write a failing test, implement the smallest passing change, and review the result.
Why use it?
It breaks development into small, verifiable changes and keeps multiple agents focused on one task and one code area at a time.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mpga plugin — 18 skills, 26 commands, 3 agents shipped together

not rated 5repo 7mo ago A scan 29 tokens original MIT

Good fit Use it to claim tasks, load their requirements, write a failing test, implement the smallest passing change, and review the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/benrben/mpga/develop
View source ↗ benrben/MPGA
Install

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.

Any agent
npx skills add benrben/MPGA --skill develop
Clone the repo
git clone --depth 1 https://github.com/benrben/MPGA

Made for: Claude Code.

Or install mpga, the plugin that ships this one along with the rest of its 18 skills, 26 commands, 3 agents.

Wrote 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.

agentmods badge for mpga-develop

README.md
[![agentmods](https://agentmods.dev/badge/skills/benrben/mpga/develop/github.svg)](https://agentmods.dev/skills/benrben/mpga/develop)
Your own site
<a href="https://agentmods.dev/skills/benrben/mpga/develop"><img src="https://agentmods.dev/badge/skills/benrben/mpga/develop/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.

agentmods 80×15 button for mpga-develop

Your own site · 80×15
<a href="https://agentmods.dev/skills/benrben/mpga/develop"><img src="https://agentmods.dev/badge/skills/benrben/mpga/develop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,313 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01313
Opus 5.5 $0.00012 $0.00525
Sonnet 5.5 $0.00006 $0.00263
Haiku 4.5 $0.00003 $0.00131

Measured 2mo ago against content hash 344141f5cde2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mpga-develop 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 2mo 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.

mpga-plugin/skills/develop/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

develop

Trigger: Plan approved, ready to execute a task. Time to Make Project Great Again.

This is the canonical TDD execution protocol. The /mpga:execute command delegates here — use /mpga:develop for all TDD cycle work.

Protocol

For each task in todo column (or a specified task):

  1. Claim the task — it's OURS now: Start the live board in the browser through Node first:

    mpga board live --serve --open

    Then claim the task:

    mpga board claim <task-id>

    Claim the scope-local write lane too. One writer per scope. ALWAYS.

  2. Load context — know what we're building:

    • Read task card: cat MPGA/board/tasks/<task-file>.md
    • Read relevant scope docs: cat MPGA/scopes/<scope>.md
    • Each TDD task runs in a focused context with only relevant scopes loaded.
    • If another task is already writing to that scope, pick a different ready task.

  3. red-green micro-cycle phase — the HEART of TDD:

    • Spawn red-dev agent with task + scope context
    • red-dev writes ONE failing test (starting with degenerate case) — bar turns RED
    • Spawn green-dev agent to make that ONE test pass with minimal code — bar turns GREEN
    • red-dev writes the NEXT test (slightly more complex) — bar turns RED again
    • green-dev makes it pass — bar turns GREEN again
    • Build complexity progressively: degenerate → simple → complex → edge cases
    • Repeat until all acceptance criteria are covered — EVERY SINGLE ONE
    • If handoff cost is dominating and the same scope/fixture is still hot, red-dev MAY queue one additional failing test. Never more than two outstanding red tests.
    • If green-dev signals "retreat-to-green" (architecture blocks): spawn blue-dev for structural refactoring, then resume micro-cycle
    • While red-dev/green-dev own the write lane, scout and auditor may run in the background as read-only helpers
    • Update stage: mpga board update <id> --tdd-stage red 
      mpga spoke 'RED phase done. Tests written and failing. Green-dev, your move.'
    • Then: mpga board update <id> --tdd-stage green 
      mpga spoke 'GREEN phase done. All tests passing. Minimal code. Blue-dev, clean it up.'

Read the full file on GitHub · 123 lines

Changes

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.

  1. 2mo ago First seen · 123 lines · 29 tokens per session scan A 344141f5cde2

Subscribe to this mod's changes

mpga-develop is a skill published in the GitHub repository benrben/MPGA (5 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 1,313 once invoked, about $0.0001 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.

TDDTesting
Related

mpga-develop compared with skills from other repositories

mpga-develop next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mpga-developbenrben/MPGASkill57mo agoMITA29Claude Code
engram-testing-coverageGentleman-Programming/engramSkill7.9ktodayMITA25Claude Code, Codex
principle-test-behavior-not-implementationmichael-denyer/pstack-claudeSkill4.2kyesterdayMITA50Claude Code
tddcodewithmukesh/dotnet-claude-kitSkill8287d agoMITA81Claude Code
nw-ddd-eventsourcingnWave-ai/nWaveSkill6354d agoMITA38Claude Code
nw-fp-clojurenWave-ai/nWaveSkill6354d agoMITA25Claude Code
nw-leanux-methodologynWave-ai/nWaveSkill6354d agoMITA37Claude Code