bmad-party-mode

bmad-party-mode is a skill for Claude Code, Codex from flanliulf/SpecLite. It costs 59 tokens per session (1,892 once invoked), scanned A, a copy of bmad-party-mode, MIT.

A discussion tool that brings several independent product or project perspectives into one conversation. “Party mode” means a roundtable discussion among multiple agents.

In plain words
What is it for?
Running group discussions, gathering multiple agent perspectives, and examining a project or decision from several roles.
Why use it?
It can surface disagreements, missing concerns, and different ideas that may be overlooked in a single review.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Running group discussions, gathering multiple agent perspectives, and examining a project or decision from several roles.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flanliulf/speclite/bmad-party-mode
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 flanliulf/SpecLite --skill bmad-party-mode
Clone the repo
git clone --depth 1 https://github.com/flanliulf/SpecLite

Made for: Claude Code, Codex.

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 bmad-party-mode

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/flanliulf/speclite/bmad-party-mode"><img src="https://agentmods.dev/badge/skills/flanliulf/speclite/bmad-party-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,892 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 100% copy Near-identical to another mod 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.00059 $0.01892
Opus 5 $0.00030 $0.00946
Sonnet 5 $0.00012 $0.00378
Haiku 4.5 $0.00006 $0.00189

Measured 10d ago against content hash bd13fd6cb0b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

bmad-party-mode 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 10d 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.

Origin

This is a copy

100% identical to bmad-party-mode — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agent/skills/bmad-party-mode/SKILL.md · 129 lines

How it starts

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

Party Mode

Facilitate roundtable discussions where BMAD agents participate as real subagents — each spawned independently via the Agent tool so they think for themselves. You are the orchestrator: you pick voices, build context, spawn agents, and present their responses. In the default subagent mode, never generate agent responses yourself — that's the whole point. In --solo mode, you roleplay all agents directly.

Why This Matters

The whole point of party mode is that each agent produces a genuinely independent perspective. When one LLM roleplays multiple characters, the "opinions" tend to converge and feel performative. By spawning each agent as its own subagent process, you get real diversity of thought — agents that actually disagree, catch things the others miss, and bring their authentic expertise to bear.

Arguments

Party mode accepts optional arguments when invoked:

  • --model <model> — Force all subagents to use a specific model (e.g. --model haiku, --model opus). When omitted, choose the model that fits the round: use a faster model (like haiku) for brief or reactive responses, and the default model for deep or complex topics. Match model weight to the depth of thinking the round requires.
  • --solo — Run without subagents. Instead of spawning independent agents, roleplay all selected agents yourself in a single response. This is useful when subagents aren't available, when speed matters more than independence, or when the user just prefers it. Announce solo mode on activation so the user knows responses come from one LLM.

On Activation

  1. Parse arguments — check for --model and --solo flags from the user's invocation.

  2. Load config from {project-root}/_bmad/core/config.yaml and resolve:

  • Use {user_name} for greeting
  • Use {communication_language} for all communications
  1. Resolve the agent roster by running:

    python3 {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key agents
    

Read the full file on GitHub · 129 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. 10d ago First seen · 129 lines · 59 tokens per session scan A bd13fd6cb0b0

Subscribe to this mod's changes

bmad-party-mode is a skill published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 1,892 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bmad-party-mode, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

lain

Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…

spuentesp/lain · 90 tokens

botpipe-workflow-authoring

Author, review, and improve Botpipe workflows. Use when Codex is asked to create packaged or workspace-local Botpipe workflows, convert codebases into workflows, design provider-heavy producer/verifier steps, write Botpipe prompts/contracts, inspect Botpipe traces, or apply Codex CLI/gpt-5.5 workflow patterns.

mrauter1/botpipe · 72 tokens

pre-merge

The CI gate. Takes a feature branch from "eng says done" to "PR open against staging with green checks". Runs the project's preflight-resolved pipeline from devkit/policy.json components[]: sync → parallel correctness + security waves → coverage → regression tail → security/migration → PRD-consistency → open PR. Emits…

ndisisnd/msg · 101 tokens

intake

The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Owns the requirements interview — fleshes out thin ideas, proactively…

ndisisnd/msg · 239 tokens

merge

The ship gate — the only skill that merges. --staging merges the feature→staging PR on green CI, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships the double-confirmed release to main and deploys production. Never self-certifies staging; nothing reaches main…

ndisisnd/msg · 94 tokens

msg

Root menu for msg skills, plus harness modes. --init is the one-time project bootstrap — use it when the user says "initialise project", "bootstrap repo", "set up the framework", "start a new project", or asks to set up project structure in an empty repo. Other modes: --init-staging (add a staging branch), --update…

ndisisnd/msg · 162 tokens