A plugin marketplace listing for bpe, a development workflow built around specifications, test-driven development, multi-step runs, validation, and continuing work across sessions. Test-driven development means writing tests that describe the expected behavior before implementing the code.

Use it to list the bpe plugin and identify its source, including its specification workflow, test-first development process, validation gate, and session continuity.

It describes what the bpe plugin provides and where its plugin source is located. This gives a marketplace the information needed to make the plugin available.

bpe — Plugin by MasonEgger

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.

Claude Code

/plugin marketplace add MasonEgger/bpe-claude-code-plugin

agentmods

npx agentmods add plugins/masonegger/bpe-claude-code-plugin/marketplace

Clone the repo

git clone --depth 1 https://github.com/MasonEgger/bpe-claude-code-plugin

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

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

.claude-plugin/marketplace.json · 15 lines

What it actually says

{
  "name": "bpe",
  "owner": {
    "name": "Mason Egger",
    "url": "https://mason.dev"
  },
  "plugins": [
    {
      "name": "bpe",
      "source": "./bpe",
      "description": "BPE (Brainstorm-Plan-Execute) development workflow: spec-driven TDD, autonomous multi-step runs with a validation gate, and cross-session continuity"
    }
  ]
}

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.

2d ago First seen · 15 lines scan A d7ae74afe1a9

Subscribe to this mod's changes

bpe is a plugin published in the GitHub repository MasonEgger/bpe-claude-code-plugin (7 stars, last pushed 10d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Productivity Testing Writing and docs

bpe

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

humanizer

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc