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-partner-apigit 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-partner-api)<a href="https://agentmods.dev/skills/vobiz-ai/agent-skills/vobiz-partner-api"><img src="https://agentmods.dev/badge/skills/vobiz-ai/agent-skills/vobiz-partner-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/vobiz-ai/agent-skills/vobiz-partner-api"><img src="https://agentmods.dev/badge/skills/vobiz-ai/agent-skills/vobiz-partner-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.00051 | $0.02276 |
| Opus 5 | $0.00026 | $0.01138 |
| Sonnet 5 | $0.00010 | $0.00455 |
| Haiku 4.5 | $0.00005 | $0.00228 |
Grade A, and why
vobiz-partner-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 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vobiz Partner API skill
Use this for white-label / reseller workflows where one master partner account owns multiple customer sub-accounts. Auth uses the same X-Auth-ID / X-Auth-Token headers as the main API - there is no separate Bearer JWT. Just use your partner-tier credentials.
Base path
https://api.vobiz.ai/api/v1/partner/*
(Routes do NOT live under /partner/v1/ - that path returns 404.)
Partner profile + dashboard
GET /api/v1/partner/me- your partner profileGET /api/v1/partner/dashboard- aggregated KPIs (total customers, balance held, MTD revenue)
Auth model in one line: partner creds (PA_…) drive /api/v1/partner/*; the customer's own creds (MA_…) drive /api/v1/Account/{customer_auth_id}/* voice ops. There is no Bearer JWT for partner server-to-server calls (JWT login is for interactive sessions only).
Customer accounts
GET /api/v1/partner/accounts- list customers. Pagination params arepage+per_page(default 20); the response echoesper_pageback assize.searchsubstring-matches name or email.POST /api/v1/partner/accounts- create customer. Required:name, email, phone, password, country. Optional (guaranteed):company. Returns201with the customer's ownauth_id+auth_token- theauth_tokenis shown only once; store it encrypted, it's the customer's API credential.emailmust be platform-unique;passwordneeds 8+ chars with a number and special char.GET /api/v1/partner/accounts/{customer_auth_id}- full customer profile (re-fetchesauth_token).GET /api/v1/partner/accounts/{customer_auth_id}/balance- real-time wallet (cash_credits).
Balance transfer
POST /api/v1/partner/accounts/{customer_auth_id}/transfer-balance- atomic debit/credit. Body:{amount, currency, description?}.currencymust equal your partner currency (no FX conversion). Permanent - cannot be reversed; no idempotency key (poll customer transactions before retrying a timed-out request).400on insufficient partner balance (current_balance/requested_amountin payload) or currency mismatch;404if the customer isn't yours.
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 · 101 lines · 51 tokens per session scan A 03808da5542f
vobiz-partner-api is a skill published in the GitHub repository vobiz-ai/Agent-Skills (2 stars, last pushed 22d ago), licensed MIT. It adds 51 tokens to every session and 2,276 once invoked, about $0.0003 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
exact-online-webhooks
Receive and verify Exact Online webhooks. Use when setting up Exact Online webhook handlers, debugging HashCode signature verification, subscribing to topics via the WebhookSubscriptions REST endpoint, or handling entity change events like Accounts, Items, StockPositions, FinancialTransactions, GoodsDeliveries, and…
adyen-webhooks
Receive and verify Adyen webhooks (standard notifications). Use when setting up Adyen webhook handlers, debugging HMAC signature verification, or handling payment events like AUTHORISATION, CAPTURE, REFUND, CANCELLATION, and CHARGEBACK.
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.
bridge-api-webhooks
Receive and verify Bridge API webhooks (bridgeapi.io — the open-banking aggregator by Bridge/Bankin', NOT bridge.xyz). Use when setting up Bridge API webhook handlers, debugging BridgeApi-Signature HMAC-SHA256 verification, or handling events like item.created, item.refreshed, item.account.updated…
bridge-xyz-webhooks
Receive and verify Bridge (bridge.xyz) webhooks. Use when setting up Bridge webhook handlers, debugging RSA signature verification of the X-Webhook-Signature header, or handling stablecoin/fiat events like customer.updated, kyclink.updated, transfer.updated, and virtualaccount.activity.
circle-webhooks
Receive and verify Circle Payments Network (CPN) v2 webhooks. Use when setting up Circle webhook handlers, debugging ECDSA signature verification (X-Circle-Signature, X-Circle-Key-Id), or handling notifications like cpn.payment., cpn.transaction., and cpn.rfi..