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 agentmods add skills/br3eze-code/br3eze-code/billing-payments-specialistnpx skills add br3eze-code/br3eze-code --skill billing-payments-specialistgit clone --depth 1 https://github.com/br3eze-code/br3eze-codeWrote 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/br3eze-code/br3eze-code/billing-payments-specialist)<a href="https://agentmods.dev/skills/br3eze-code/br3eze-code/billing-payments-specialist"><img src="https://agentmods.dev/badge/skills/br3eze-code/br3eze-code/billing-payments-specialist.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00336 |
| Opus 5 | $0.00019 | $0.00168 |
| Sonnet 5 | $0.00008 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
billing-payments-specialist 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 4d 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.
What it actually says
Billing and Payments Specialist
Protect financial correctness and customer trust by separating calculation, authorization, settlement, reconciliation, and refund operations.
Workflow
- Validate tenant, customer, order, amount, currency, tax context, payment method, idempotency key, and authority.
- Recalculate or verify the amount from trusted product and pricing records; never trust client totals.
- Authorize the payment or credit and record provider response without exposing sensitive payment data.
- Settle, refund, reverse, or credit only through explicit state transitions and policy gates.
- Reconcile provider transactions with internal ledger entries and surface mismatches for review.
- Record immutable activity evidence, redacted provider identifiers, actor, timestamp, and outcome.
Boundaries
Pricing and Promotions proposes calculations. Orders and Checkout owns order intent. Catalog owns product definitions. Procurement owns supplier commitments. Voucher and Access owns entitlement state. Billing owns the financial ledger and must not silently change operational or network state.
Controls
Use integer minor units, explicit currencies, idempotency, authorization checks, least-privilege access, redacted logs, retry-safe provider calls, webhook signature validation, replay protection, and reconciliation jobs. Require approval for refunds, credits, manual adjustments, high-value transactions, and exceptions.
Never log raw card data, credentials, voucher secrets, or full payment tokens. Treat provider callbacks as untrusted until authenticated and matched to a known transaction.
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.
- 4d ago First seen · 28 lines · 39 tokens per session scan A 06394d812f82
billing-payments-specialist is a skill published in the GitHub repository br3eze-code/br3eze-code (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 39 tokens to every session and 336 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
ap-master
应付账款主流程 — 整合付款排期 + 三单匹配 + 供应商审核的完整 AP 周期。 适用情形：每周固定时间（如周二）执行，整合到期应付清单、 三单匹配、付款审核全流程，生成可执行的付款指令。 核心：到期分析 → 三单匹配 → 优先级排序 → 审批 → 付款指令。.
reconcile
Reconcile today's fulfilments against the ledger and report any mismatches.
paypal-integration
Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-commerce checkout flows.
stripe-integration
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.
alpha-vantage
Access real-time and historical stock market data, forex rates, cryptocurrency prices, commodities, economic indicators, and 50+ technical indicators via the Alpha Vantage API. Use when fetching stock prices (OHLCV), company fundamentals (income statement, balance sheet, cash flow), earnings, options data, market…
asc-ppp-pricing
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.