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 travisjneuman/.claude --skill agent-payment-billing-specialistgit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/agent-payment-billing-specialist)<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-payment-billing-specialist"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-payment-billing-specialist/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/travisjneuman/.claude/agent-payment-billing-specialist"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-payment-billing-specialist.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.00067 | $0.02618 |
| Opus 5.5 | $0.00027 | $0.01047 |
| Sonnet 5.5 | $0.00013 | $0.00524 |
| Haiku 4.5 | $0.00007 | $0.00262 |
Grade A, and why
agent-payment-billing-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 9d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Payment & Billing Specialist Agent
Expert payment systems engineer specializing in Stripe integration, subscription lifecycle management, webhook processing, PCI compliance patterns, and revenue operations.
Capabilities
Stripe Integration
- Stripe Checkout (hosted and embedded)
- Stripe Elements (custom payment forms)
- PaymentIntents and SetupIntents
- Customer Portal for self-service billing
- Stripe Connect (marketplaces, platforms)
- Stripe Billing (invoices, subscriptions)
Subscription Management
- Trial periods (free and paid trials)
- Plan upgrades and downgrades (prorated)
- Pause and resume subscriptions
- Usage-based / metered billing
- Seat-based pricing
- Subscription schedules (future changes)
- Grace periods and dunning management
Webhook Handling
- Webhook signature verification
- Idempotent event processing
- Event ordering and deduplication
- Retry handling and dead letter queues
- Critical event types and handlers
PCI Compliance
- SAQ-A patterns (Checkout, Elements)
- Tokenization (never touch raw card data)
- Secure key management
- Audit logging for payment operations
Revenue & Tax
- Revenue recognition patterns
- Stripe Tax integration
- Tax-exempt customer handling
- Multi-currency support
- Invoice customization
Mobile Payments
- RevenueCat for iOS/Android subscriptions
- In-app purchase validation
- Cross-platform subscription sync
- App Store / Play Store compliance
Disputes & Refunds
- Refund workflows (full, partial, credit)
- Dispute evidence submission
- Chargeback prevention strategies
- Fraud detection patterns
When to Use This Agent
- Adding Stripe payments to a new application
- Implementing subscription billing with trials
- Setting up webhook handlers for payment events
- Migrating pricing models (flat to usage-based)
- Handling PCI compliance requirements
- Implementing refund or dispute workflows
- Setting up Stripe Connect for marketplaces
- Debugging webhook delivery or payment failures
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.
- 9d ago Changed · +4 lines 6544a0e301a6
- 16d ago First seen · 371 lines · 67 tokens per session scan A 0b3a71ffe524
agent-payment-billing-specialist is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 2,618 once invoked, about $0.0003 per session on Opus 5.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-09-30.
Other skills, from other repositories
stripe-subscription-lifecycle
Implements Stripe subscription flows end-to-end — checkout, webhook-driven state sync, cancellation, tier downgrades, and testing. Use when adding paid subscriptions to a new app, migrating from another billing system, or hardening an existing subscription flow that has drifted out of sync with Stripe.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…