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/awesome-pexip-skills --skill project-intakegit clone --depth 1 https://github.com/Josh-E-S/awesome-pexip-skillsWrote 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/awesome-pexip-skills/project-intake)<a href="https://agentmods.dev/skills/josh-e-s/awesome-pexip-skills/project-intake"><img src="https://agentmods.dev/badge/skills/josh-e-s/awesome-pexip-skills/project-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.
<a href="https://agentmods.dev/skills/josh-e-s/awesome-pexip-skills/project-intake"><img src="https://agentmods.dev/badge/skills/josh-e-s/awesome-pexip-skills/project-intake.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.00121 | $0.01999 |
| Opus 5 | $0.00060 | $0.01000 |
| Sonnet 5 | $0.00024 | $0.00400 |
| Haiku 4.5 | $0.00012 | $0.00200 |
Grade A, and why
project-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 12d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pexip project intake
Pexip apps have many shapes — a one-page demo, an embedded widget, a full white-labeled clone of webapp3. The right skill set, dependencies, and architecture choices differ a lot. Don't guess. Ask the user a small number of targeted questions, then route to the right skills.
Keep it brief. Most projects need 3–4 questions answered, not 10.
Critical rule: don't fabricate test endpoints
Never offer a specific demo URL, hostname, or test-VMR alias unless the user provided it or you've verified it from current docs. If the user wants to test:
- Ask if they have a Pexip Infinity deployment they already use
- Ask if they have a node a colleague can share
- Suggest contacting Pexip via their official channels for a trial
Do not offer plausible-sounding hostnames like demo.pexip.example or meet.example.com. Either it'll be a dead URL or it'll route somewhere unintended. Either way, the user wastes time.
The minimum questions
Ask one at a time, with multiple-choice options where possible. Stop as soon as you have enough to recommend the right skills.
Q1. What are you building? (always ask)
A) A new standalone Pexip app from scratch
B) Adding Pexip video to an existing app (web component, page, modal)
C) Customizing/branding webapp3 itself
D) Building a Pexip plugin (iframe inside the meeting UI)
E) Other — please describe
Routing:
- A → core skills (signals-pattern, call-lifecycle, media-pipeline, preflight, reconnect)
- B → same core skills, but with a "minimal embed" framing — usually skip preflight, simplify branding
- C → branding-manifest is the primary skill; user usually doesn't need to write call code
- D → plugin-host (note: that skill is the host side; for plugin-author docs, point to Pexip's separate plugin SDK docs)
- E → ask follow-up
Q2. Which features matter for v1? (always ask)
[ ] Audio/video call (always required)
[ ] Screen sharing
[ ] Chat (group)
[ ] Direct messages (1:1)
[ ] Participant list with mute/admit/kick
[ ] Background blur/replace
[ ] Live captions
[ ] Breakout rooms
[ ] Layout selection
[ ] Far-end camera control (PTZ — rare, hardware-specific)
[ ] Plugin support
[ ] Custom branding (colors, logo, hidden buttons)
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.
- 12d ago First seen · 218 lines · 121 tokens per session scan A 48d13dfe3a63
project-intake is a skill published in the GitHub repository Josh-E-S/awesome-pexip-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 121 tokens to every session and 1,999 once invoked, about $0.0006 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…