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 vobiz-ai/Agent-Skills --skill vobiz-applications-endpointsgit clone --depth 1 https://github.com/vobiz-ai/Agent-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/vobiz-ai/agent-skills/vobiz-applications-endpoints)<a href="https://agentmods.dev/skills/vobiz-ai/agent-skills/vobiz-applications-endpoints"><img src="https://agentmods.dev/badge/skills/vobiz-ai/agent-skills/vobiz-applications-endpoints/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/vobiz-ai/agent-skills/vobiz-applications-endpoints"><img src="https://agentmods.dev/badge/skills/vobiz-ai/agent-skills/vobiz-applications-endpoints.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.00040 | $0.01898 |
| Opus 5 | $0.00020 | $0.00949 |
| Sonnet 5 | $0.00008 | $0.00380 |
| Haiku 4.5 | $0.00004 | $0.00190 |
Grade A, and why
vobiz-applications-endpoints 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 11d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vobiz Applications & Endpoints skill
Two related but distinct concepts:
- Application: a named container that holds the
answer_url/hangup_urlwebhooks. Phone numbers and endpoints get attached to an application so calls fire the configured webhooks. - Endpoint: a SIP user account (
username+password+alias) for soft-phones, browser WebRTC clients, or IP desk-phones to register with Vobiz.
Base URL: https://api.vobiz.ai. Auth headers on every request: X-Auth-ID + X-Auth-Token.
Application vs Endpoint - which do I need?
- Inbound call to a phone number (DID) → create an Application, then attach the number to it.
- A person or device that needs to place/receive calls (browser, softphone, desk phone, AI agent) → create an Endpoint, then attach an Application to the endpoint for its call-handling logic.
- Both: number routes inbound to an Application; that Application's VobizXML can
Dialthe endpoint'ssip_urito ring the device.
Application endpoints
| Op | Path | Notes |
|---|---|---|
| Create | POST /api/v1/Account/{auth_id}/Application/ |
Body: {app_name, answer_url, answer_method, hangup_url?, hangup_method?, ...}. Returns app_id. |
| List | GET /api/v1/Account/{auth_id}/Application/ |
Paginated: limit (default 20, max 100), offset (default 0). |
| Get | GET /api/v1/Account/{auth_id}/Application/{app_id}/ |
|
| Update | POST /api/v1/Account/{auth_id}/Application/{app_id}/ |
(yes, POST not PUT.) Partial update; omitted fields unchanged. |
| Delete | DELETE /api/v1/Account/{auth_id}/Application/{app_id}/ |
204 on success; 409 if numbers are still attached. |
Attach / detach a number (different path - under numbers, not Application)
| Op | Path |
|---|---|
| Attach | POST /api/v1/Account/{auth_id}/numbers/{number}/application body {application_id} |
| Detach | DELETE /api/v1/Account/{auth_id}/numbers/{number}/application |
{number} is the E.164 number URL-encoded (+ → %2B, e.g. %2B14155551234).
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.
- 11d ago First seen · 104 lines · 40 tokens per session scan A 189159da2148
vobiz-applications-endpoints is a skill published in the GitHub repository vobiz-ai/Agent-Skills (2 stars, last pushed 23d ago), licensed MIT. It adds 40 tokens to every session and 1,898 once invoked, about $0.0002 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
architecture-decision-record
ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.
azure-event-grid-webhooks
Receive and validate Azure Event Grid webhook deliveries. Use when setting up an Event Grid WebHook event handler, implementing the Microsoft.EventGrid.SubscriptionValidationEvent handshake (echo data.validationCode as validationResponse with HTTP 200), implementing the CloudEvents v1.0 HTTP OPTIONS abuse-protection…
baselinker-webhooks
Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: orderid, state), there is NO signature…
cronofy-webhooks
Receive and verify Cronofy push notifications (webhooks). Use when setting up Cronofy notification channels, debugging Cronofy-HMAC-SHA256 verification, or handling Cronofy calendar events like verification, change, profiledisconnected, conferencingprofiledisconnected, profileinitialsynccompleted, and gdprrequested.…
clio-webhooks
Receive and verify Clio (Clio Manage) webhooks. Use when setting up Clio webhook handlers, debugging X-Hook-Signature verification, completing the X-Hook-Secret handshake, or handling legal practice events like matter.created, contact.updated, activity.created, or bill events.
favro-webhooks
Receive and verify Favro webhooks. Use when setting up Favro webhook handlers, debugging X-Favro-Webhook signature verification, accepting the setup ping, or handling card events (card.created, card.committed, card.moved, card.updated, card.deleted) and comment events (comment.created, comment.updated…