A workflow for test-driven development (TDD), where each task is guided by a failing test, an implementation that passes it, cleanup, and review.

Use it to develop a new task, work on a phase of tasks, run supporting checks, and review edge cases before completion.

It coordinates the work, keeps changes tied to acceptance criteria, and records evidence before a task is marked done.

develop — Command for Claude Code by 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.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/benrben/mpga/develop/github.svg)](https://agentmods.dev/commands/benrben/mpga/develop)

Your own site

<a href="https://agentmods.dev/commands/benrben/mpga/develop"><img src="https://agentmods.dev/badge/commands/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/benrben/mpga/develop"><img src="https://agentmods.dev/badge/commands/benrben/mpga/develop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 306 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00306
Opus 5.5	$0.00000	$0.00122
Sonnet 5.5	$0.00000	$0.00061
Haiku 4.5	$0.00000	$0.00031

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

Security

Grade A, and why

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/commands/develop.md · 23 lines

What it actually says

/mpga:develop

Orchestrate the TDD cycle for a task (red → green → blue → review). Tremendous cycle, believe me. MPGA alone can fix it.

Steps

Start the live board in the browser: mpga board live --serve --open
Claim the task: mpga board claim <task-id>
Load context: task card + relevant scope docs
Claim the scope-local write lane. Independent scopes may run in parallel; same-scope writers may not.
red↔green micro-cycle: red-dev writes ONE failing test (starting with degenerate case), green-dev makes it pass, repeat until all acceptance criteria covered. If handoff overhead dominates, allow one extra queued failing test in the same hot scope. If green-dev hits an architectural wall, blue-dev does a structural refactor mid-cycle.
Let scout / auditor run in the background as read-only helpers
blue-dev: refactor both production code and tests (without changing assertions)
reviewer: review for quality, testability, and degenerate case coverage
Use verifier for milestone boundaries, risky tasks, or explicit full verification
Record evidence and move task to done — Great job! Ready for peace — zero merge conflicts

Usage

/mpga:develop
/mpga:develop T001

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.

2mo ago First seen · 23 lines · 0 tokens per session scan A ec5338c3ffcd

Subscribe to this mod's changes

develop is a command published in the GitHub repository benrben/MPGA (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 306 tokens. 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.

TDD Testing

develop next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
developbenrben/MPGA	Command	5	7mo ago	MIT	A	0	Claude Code
bugfixnWave-ai/nWave	Command	635	4d ago	MIT	A	18	Claude Code
hub-tddKastalien-Research/thoughtbox	Command	65	yesterday	MIT	A	27	Claude Code
task-verifythixpin/pitway	Command	20	21d ago	MIT	A	0	Claude Code
usage-addthixpin/pitway	Command	20	21d ago	MIT	A	0	Claude Code
milestone-listthixpin/pitway	Command	20	21d ago	MIT	A	0	Claude Code
speckit.tdd.planarrrrny/zuraffa	Command	5	3d ago	MIT	A	37	Claude Code