What is pexip-mgmt-intake?

An intake guide for open-ended Pexip Infinity administration tasks. Pexip Infinity is software for running video-conferencing services.

It helps scope operator actions, recurring reports, configuration changes, integrations, and development work on Pexip tools.

It first narrows down what kind of management or API task you need, instead of assuming the wrong approach.

pexip-mgmt-intake — Skill for Claude Code by Josh-E-S/pexip-mgmt-mcp

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 Josh-E-S/pexip-mgmt-mcp --skill pexip-mgmt-intake

Clone the repo

git clone --depth 1 https://github.com/Josh-E-S/pexip-mgmt-mcp

Made for: Claude Code.

Or install pexip-mgmt, the plugin that ships this one along with the rest of its 10 skills, 1 MCP server.

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/skills/josh-e-s/pexip-mgmt-mcp/pexip-mgmt-intake/github.svg)](https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-mgmt-intake)

Your own site

<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-mgmt-intake"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-mgmt-intake/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/skills/josh-e-s/pexip-mgmt-mcp/pexip-mgmt-intake"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-mgmt-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,788 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.00143	$0.01788
Opus 5.5	$0.00057	$0.00715
Sonnet 5.5	$0.00029	$0.00358
Haiku 4.5	$0.00014	$0.00179

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

Security

Grade A, and why

pexip-mgmt-intake 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.

pexip-mgmt-skills/skills/_intake/pexip-mgmt-intake/SKILL.md · 184 lines

How it starts

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

Pexip management intake

A management-side Pexip task can be many shapes: a one-off operator action ("kick this person"), a recurring report ("daily call volume"), a configuration push ("add 50 VMRs"), an integration extension ("build a webhook receiver"), or a developer task on the MCP server itself ("add a tool for X"). The right skill set, dependencies, and operational stance differ a lot.

Don't guess. Ask a small number of targeted questions, then route.

Keep it brief. Most management tasks resolve in 2-3 questions.

When to use

Any "I want to use Pexip's management API to…" type request
Any "automate" / "report" / "monitor" Pexip request without scope
The user mentioned Pexip and the MCP server but not what they're trying to do

When NOT to use

Narrow API questions: "what's the schema for conference?" → answer with pexip-config-api
Live operator verbs: "kick Alice", "lock the AllHands" → answer with pexip-operations
Specific tool questions: "how do I call summarize_calls?" → answer with pexip-operations
MCP server code edits: "add a tool that wraps X" → answer with the matching pexip-*-api developer-reference skill

The minimum questions

Ask one at a time, with options where possible. Stop as soon as you have enough to route.

Q1. What are you trying to do? (always ask)

A) One-off operator action against a live or recent meeting
   (kick, lock, transfer, change layout, check who's in)
B) Recurring reporting or monitoring
   (daily / weekly call volume, quality forensics, alarm dashboard)
C) Bulk configuration change
   (create N VMRs, update dial-plan rules, manage end users)
D) Extend the MCP server itself
   (add a new tool, wrap a Pexip endpoint not currently covered)
E) Build a webhook receiver for Pexip events
   (event sinks pushing to a custom HTTP listener)
F) Integrate Pexip with a room system (MJX / One-Touch Join)
G) Other — please describe

Routing:

A → pexip-operations (operator runbook, all live-meeting playbooks)
B → pexip-operations → reporting.md (or platform-health.md for alarm-style monitoring)
C → pexip-operations → vmr-administration.md and / or dial-plan.md
D → the matching developer-reference skill:
- Configuration CRUD → pexip-config-api
- Live state reads → pexip-status-api
- CDR / history reads → pexip-history-api
- Live commands (kick/lock/transfer) → pexip-command-api
E → pexip-event-sinks
F → pexip-mjx
G → ask follow-up

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

2mo ago First seen · 184 lines · 143 tokens per session scan A a1a886d537a3

Subscribe to this mod's changes

pexip-mgmt-intake is a skill published in the GitHub repository Josh-E-S/pexip-mgmt-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 143 tokens to every session and 1,788 once invoked, about $0.0006 per session on Opus 5.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.

pexip-mgmt-intake next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pexip-mgmt-intakeJosh-E-S/pexip-mgmt-mcp	Skill	1	7d ago	MIT	A	143	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code