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.
npx agentmods add commands/teammanagementplugin/claude-plugin/custom-protocol-update-after-reinstallgit clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWrote 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.
[](https://agentmods.dev/commands/teammanagementplugin/claude-plugin/custom-protocol-update-after-reinstall)<a href="https://agentmods.dev/commands/teammanagementplugin/claude-plugin/custom-protocol-update-after-reinstall"><img src="https://agentmods.dev/badge/commands/teammanagementplugin/claude-plugin/custom-protocol-update-after-reinstall.svg" alt="Measured on agentmods" height="20"></a>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.00011 | $0.00499 |
| Opus 5 | $0.00005 | $0.00249 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
custom-protocol-update-after-reinstall 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Custom Protocols After Reinstall
After a team-management reinstall/update, the built-in (system) protocols may have changed. This reconciles your forked custom protocols (created via /team-management:custom-protocol-create) against the new system versions.
Workflow
- Detect drift. Call
mcp__plugin_team-management_tm__protocol_check_drift(). - Report the result:
drifted— each entry's system source changed since you forked it. The new system version has been staged next to your custom copy asnew-<basename>(e.g.custom/new-task.json,custom/sub-protocols/new-task-investigation.md). Show the user eachcustompath and itsstagedcounterpart.unknown— custom protocols with no provenance record (hand-made forks, or forked before provenance tracking). The tool cannot diff these; list them so the user knows they are untracked.- If
driftedis empty, tell the user everything is up to date and stop here.
- Guide the merge, one file at a time. For each drifted file, read both the user's
custom/<file>and the stagednew-<file>, and help the user fold the upstream changes they want to keep into their custom version. Leave the stagednew-file untouched until they confirm. - Finalize. Once the user confirms all merges are done, call
mcp__plugin_team-management_tm__protocol_check_drift(acknowledge=True). This deletes thenew-staged files and refreshes the provenance hashes so the next run starts clean. Reportremoved_stagingandacknowledged.
Rules
- Do NOT read or edit files under
team-management/protocol-configs/system/— it is protected; the MCP tool reads it for you. - The staged
new-<file>copies live incustom/but are NOT active protocols —protocol_listignores thenew-prefix, and the engine never resolves them. They are scratch copies for merging only. - Only call
acknowledge=Trueafter the user has finished merging — it discards the staged versions and resets the drift baseline.
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.
- 3d ago First seen · 25 lines · 11 tokens per session scan A 3fbd22b73925
custom-protocol-update-after-reinstall is a command published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 28d ago), licensed MIT. It adds 11 tokens to every session and 499 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.
Other commands, from other repositories
research
Research a technical or product question.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.