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 skills/josh-e-s/pexip-mgmt-mcp/pexip-command-apinpx skills add Josh-E-S/pexip-mgmt-mcp --skill pexip-command-apigit clone --depth 1 https://github.com/Josh-E-S/pexip-mgmt-mcpWrote 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/skills/josh-e-s/pexip-mgmt-mcp/pexip-command-api)<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-command-api"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-command-api.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.1 | $0.00185 | $0.01889 |
| Opus 5 | $0.00093 | $0.00945 |
| Sonnet 5 | $0.00037 | $0.00378 |
| Haiku 4.5 | $0.00018 | $0.00189 |
Grade A, and why
pexip-command-api 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 5d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pexip Infinity Management — Command API
POST-only API for acting on running conferences and participants. Distinct from:
- Configuration API (CRUD on persistent platform objects)
- Status API (read-only live state)
- History API (post-call CDRs)
Commands are imperative ("disconnect this participant"), not declarative ("delete this VMR").
Base URL
https://<management-node-host>/api/admin/command/v1/<scope>/<command>/
<scope>is typicallyconference,participant, orplatform.- All commands are POST (even read-ish ones — that is the API convention).
- Auth, rate limit, schema introspection same as the other admin APIs (Basic over HTTPS, 1,000/60s,
…/schema/?format=json). - Response is
200 OKwith a small JSON body, often{"status": "success", "data": {...}}or just{"status": "success"}.
Targeting an instance
Most commands need to identify which conference instance or participant to act on. Two patterns appear, depending on the command:
conference_id+participant_idin the POST body — Pexip-internal UUIDs that you obtain from the Status API (/api/admin/status/v1/conference/<id>/or/participant/<id>/).conference_name(the dialed alias) in the POST body — for commands that act on the conference as a whole and you only know it by name.
Always introspect the schema (…/schema/?format=json) for the exact required field names per command — they shifted between Pexip versions.
Participant commands
/api/admin/command/v1/participant/<command>/
| Command | Effect | Typical body |
|---|---|---|
dial |
Dial a new participant into a conference. | conference_alias (or destination), protocol (sip/h323/mssip/rtmp/teams/gms/auto), call_type (audio/video/video-only/audio-video), role (chair/guest), system_location, streaming (bool), remote_display_name, dtmf_sequence |
disconnect |
Disconnect a single participant. | participant_id |
mute / unmute |
Audio mute one participant. | participant_id |
video_mute / video_unmute |
Video mute one participant. | participant_id |
set_role |
Change role to chair or guest. |
participant_id, role |
spotlight_on / spotlight_off |
Pin a participant in the layout. | participant_id |
transfer |
Move participant to another conference. | participant_id, conference_alias, optional role, pin |
dtmf |
Send DTMF tones into the call. | participant_id, digits |
set_text_overlay |
Display caption text under participant. | participant_id, text |
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.
- 5d ago First seen · 112 lines · 185 tokens per session scan A e94f7b43e626
pexip-command-api is a skill published in the GitHub repository Josh-E-S/pexip-mgmt-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 185 tokens to every session and 1,889 once invoked, about $0.0009 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…