What is custom-protocol-create?

A command for copying a built-in team protocol into a custom directory so its steps, modes, functions, and text can be edited.

Use it to list available protocols, choose one, and create a customizable fork under team-management/protocol-configs/custom/.

It lets a team adapt an existing workflow without changing the original system protocol, with the custom copy taking priority.

custom-protocol-create — Command by TeamManagementPlugin

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.

agentmods

npx agentmods add commands/teammanagementplugin/claude-plugin/custom-protocol-create

Clone the repo

git clone --depth 1 https://github.com/TeamManagementPlugin/claude-plugin

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

When invoked 520 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00012	$0.00520
Opus 5	$0.00006	$0.00260
Sonnet 5	$0.00002	$0.00104
Haiku 4.5	$0.00001	$0.00052

Measured yesterday against content hash 23c07cbfd039, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

custom-protocol-create 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 yesterday.

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.

plugin/commands/custom-protocol-create.md · 28 lines

How it starts

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

Create a Custom Protocol

Fork one of the built-in (system) protocols into team-management/protocol-configs/custom/ so you can edit its steps, modes, funcs, and step text freely. The engine resolves custom/ over system/, so your fork takes effect immediately — no further wiring needed.

Workflow

List the available protocols. Call mcp__plugin_team-management_tm__protocol_list(). For each protocol, present to the user:
- its name and one-line description, and
- its steps in order — each step's name, mode, and description (from the steps field),
so the user understands how the protocol works and can choose which one to take as a base / rewrite.
If the user passed a protocol name as the argument, confirm it appears in the list, then skip to step 4 with that choice.
Otherwise ask which protocol to fork with AskUserQuestion — one option per protocol, the option description summarizing what that protocol does. (The widget appends an "Other" option automatically — do not add one.)
Fork it. Call mcp__plugin_team-management_tm__protocol_customize(protocol_name="<choice>").
- If the result lists files under skipped, a previous fork already exists; those files were preserved. Tell the user, and only re-run with force=True on their explicit confirmation (it overwrites their edits).
Report the created (and any skipped) file paths plus the next_steps text. Tell the user to edit the copied files under team-management/protocol-configs/custom/, and that the engine now resolves their custom versions over system automatically.

Rules

Do NOT read or edit files under team-management/protocol-configs/system/ — it is a protected path; the MCP tool reads it for you inside the server process.
Do NOT try to copy protocol files with Bash/Edit/Write — sessions-enforce blocks reads of system/. Only protocol_customize (MCP server, hook-exempt) can do the copy.
After a future team-management reinstall, run /team-management:custom-protocol-update-after-reinstall to reconcile upstream changes against your fork.

Read the full file on GitHub · 28 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.

yesterday First seen · 28 lines · 12 tokens per session scan A 23c07cbfd039

Subscribe to this mod's changes

custom-protocol-create is a command published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 12 tokens to every session and 520 once invoked, about $0.0001 per session on Opus 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.

Code review agentic-workflows ai-agents anthropic claude claude-code claude-plugin

custom-protocol-create

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Create a Custom Protocol

Workflow

Rules

What this file has done since we first saw it

Other commands, from other repositories

research

brand-setup

save

screens

graphify

index