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 skills add Josh-E-S/pexip-mgmt-mcp --skill pexip-history-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-history-api)<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-history-api"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-history-api/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.
<a href="https://agentmods.dev/skills/josh-e-s/pexip-mgmt-mcp/pexip-history-api"><img src="https://agentmods.dev/badge/skills/josh-e-s/pexip-mgmt-mcp/pexip-history-api.svg" alt="Reviewed on agentmods" width="80" 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.00155 | $0.01548 |
| Opus 5.5 | $0.00062 | $0.00619 |
| Sonnet 5.5 | $0.00031 | $0.00310 |
| Haiku 4.5 | $0.00015 | $0.00155 |
Grade A, and why
pexip-history-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 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pexip Infinity Management — History API
Read-only API for finished conferences and the participants who were in them. This is the source for CDRs, usage reporting, billing exports, and call-quality forensics.
Base URL
https://<management-node-host>/api/admin/history/v1/<resource>/
- Auth, rate limit, listing/filtering/schema introspection identical to the other admin APIs.
- GET only.
- A conference instance moves from Status to History the moment its last participant disconnects.
Retention
- The Management Node retains up to 10,000 conference instances plus all their participants. Beyond that, oldest entries are deleted FIFO.
- For long-term retention, export to an external warehouse on a schedule (event sinks or periodic History API pulls).
Core resources
conference/ — completed conference instances
/api/admin/history/v1/conference/
Fields include: name, service_type, tag, start_time, end_time, duration (seconds), instance_id, participant_count.
Common queries:
?start_time__gte=2026-04-01T00:00:00&start_time__lt=2026-05-01T00:00:00— calendar-month report.?service_type=conference&order_by=-start_time&limit=50— most recent VMR meetings.?name=team-standup— every past instance of a specific VMR.
participant/ — completed participant call legs
/api/admin/history/v1/participant/
Fields include:
- Identity:
display_name,remote_address,local_alias,protocol,call_direction(in/out),call_uuid,conversation_id. - Membership:
conference(the parent conference name),conference_name,role,service_tag,system_location. - Timing:
connect_time,disconnect_time,duration. - Outcome:
disconnect_reason(e.g.Call disconnected,Participant disconnected,Conference terminated,Call rejected,Call failed). - Quality summary:
call_quality('1_good'/'2_ok'/'3_bad'/'4_terrible'). - Media stream summary:
media_streams— a list of{media_type, rx_bitrate, tx_bitrate, rx_packet_loss, tx_packet_loss, rx_resolution, tx_resolution, rx_codec, tx_codec, ...}per stream the participant had.
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 · 94 lines · 155 tokens per session scan A e808ce463320
pexip-history-api is a skill published in the GitHub repository Josh-E-S/pexip-mgmt-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 155 tokens to every session and 1,548 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-history-api compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pexip-history-apiJosh-E-S/pexip-mgmt-mcp | Skill | 1 | 7d ago | MIT | A | 155 | Claude Code |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 69k | yesterday | Apache-2.0 | A | 217 | Claude Code, Codex |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 78 | Claude Code |
| fastapi-router-pymicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 46 | Claude Code |
| dev-runtimelangwatch/langwatch | Skill | 5.0k | today | Apache-2.0 | A | 172 | Claude Code |
| api-designericrisco/rsc-harness | Skill | 529 | 4d ago | MIT | A | 105 | Claude Code, Codex |
| migrate-segw-to-raparc-mcp/arc-1 | Skill | 253 | yesterday | MIT | A | 106 | Claude Code |