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-sub-accountsgit 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-sub-accounts)<a href="https://agentmods.dev/skills/vobiz-ai/agent-skills/vobiz-sub-accounts"><img src="https://agentmods.dev/badge/skills/vobiz-ai/agent-skills/vobiz-sub-accounts/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-sub-accounts"><img src="https://agentmods.dev/badge/skills/vobiz-ai/agent-skills/vobiz-sub-accounts.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.00059 | $0.02656 |
| Opus 5 | $0.00030 | $0.01328 |
| Sonnet 5 | $0.00012 | $0.00531 |
| Haiku 4.5 | $0.00006 | $0.00266 |
Grade A, and why
vobiz-sub-accounts scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "$BASE/accounts/$MA/sub-accounts/" -H "X-Auth-ID: $MA" -H "X-Auth-Token: $MA_TOK" \ How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vobiz Sub-Accounts skill
Use this when the user wants to isolate environments (dev/staging/prod), separate teams (sales vs support), or carve their account into business units with independent credentials, numbers, and CDR streams under the same parent invoice — and, for customer_use sub-accounts, verify each customer's own KYC before it can place calls.
Difference from Partner sub-accounts
| Sub-Account | Partner customer account | |
|---|---|---|
| Parent | Your own account | Partner account |
| Billing | Rolled into parent invoice | Separate wallet, transferred from partner |
| KYC | personal_use inherits parent's; customer_use does its own |
Requires its own KYC |
| API | /api/v1/accounts/{auth_id}/sub-accounts/* |
/api/v1/partner/accounts/* |
If the user wants to resell to external customers, they need the Partner API (see vobiz-partner-api skill). Sub-accounts are for internal segmentation or for vending a customer_use tenant that runs its own KYC.
Two credential pairs (the rule that prevents most bugs)
- Parent
X-Auth-ID/X-Auth-Token(MA_…): used for all provisioning and administration — CRUD on sub-accounts, all KYC calls, buying/assigning numbers. The sub-account is named by{sub_auth_id}in the URL. - Sub-account
auth_id/auth_token(SA_…): returned once at creation; the sub-account's runtime key for placing/receiving calls and pulling its own CDRs.
Rule of thumb: setting it up → authenticate as the parent; using the service → the sub-account authenticates as itself. KYC is not an exception — it is a parent-authenticated call.
CRUD endpoints
| Op | Path | Notes |
|---|---|---|
| List | GET /api/v1/accounts/{auth_id}/sub-accounts/ |
Note plural, lowercase accounts. Paginated (page, size). |
| Create | POST /api/v1/accounts/{auth_id}/sub-accounts/ |
Body: {name, email?, password?, kyc_mode?, business_type?, enabled?, rate_limit?, permissions?}. Only name is required. |
| Get | GET /api/v1/accounts/{auth_id}/sub-accounts/{sub_auth_id} |
auth_token masked here. |
| Update | PUT /api/v1/accounts/{auth_id}/sub-accounts/{sub_auth_id} |
Body: {name?, enabled?, kyc_mode?}. |
| Delete | DELETE /api/v1/accounts/{auth_id}/sub-accounts/{sub_auth_id} |
Permanent; revokes credentials. |
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 · 133 lines · 59 tokens per session scan A 4c9b762c93ef
vobiz-sub-accounts is a skill published in the GitHub repository vobiz-ai/Agent-Skills (2 stars, last pushed 23d ago), licensed MIT. It adds 59 tokens to every session and 2,656 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.…
alipay-webhooks
Receive and verify Alipay (Antom / Alipay+) webhook notifications. Use when setting up Alipay webhook handlers, debugging RSA256 Signature header verification, or handling payment events like notifyPayment, notifyCapture, notifyRefund, notifyAuthorization, and notifyDispute.
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.