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/evgenii-studitskikh/claude-code-saas-studio/setup-billingnpx skills add evgenii-studitskikh/Claude-Code-SaaS-Studio --skill setup-billinggit clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-StudioWrote 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/evgenii-studitskikh/claude-code-saas-studio/setup-billing)<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/setup-billing"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/setup-billing.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.1 | $0.00039 | $0.00702 |
| Opus 5 | $0.00019 | $0.00351 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
setup-billing 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 5d 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 — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wire up the full Stripe billing integration based on the approved pricing spec: create Stripe products and prices programmatically from a config file, implement the checkout and portal flows, and build a webhook handler that is safe to deploy to production. Non-autonomous: implementation plan is presented and approved before any code is written.
Phases
- Load pricing spec — read
docs/specs/pricing.md. If it is missing or incomplete, stop and direct to/design-pricing. Confirm the Stripe account mode (test vs. live) and thatSTRIPE_SECRET_KEYandSTRIPE_WEBHOOK_SECRETare present in.env.example. - Present implementation plan — show the files that will be created:
lib/stripe/config.ts(plan definitions),lib/stripe/client.ts(server-side Stripe instance),app/api/stripe/checkout/route.ts(checkout session endpoint),app/api/stripe/portal/route.ts(customer portal endpoint),app/api/stripe/webhook/route.ts(webhook handler), and any UI components for pricing and upgrade buttons. Get approval before writing. - Implement config and client — write
lib/stripe/config.tswith plan definitions loaded from environment variables or a static config object (no hardcoded price IDs in business logic). Writelib/stripe/client.tsexporting a server-only Stripe instance. Show files before writing. - Implement checkout and portal — write the checkout session route handler (creating or retrieving the Stripe Customer, setting
success_urlandcancel_url, attaching metadata for tenant/user ID) and the customer portal handler. Both must validate that the requesting user is authenticated via Supabase Auth. - Implement webhook handler — write
app/api/stripe/webhook/route.tsthat: (a) reads the raw request body usingrequest.text(), (b) callsstripe.webhooks.constructEventwithSTRIPE_WEBHOOK_SECRET, (c) handlescheckout.session.completed,customer.subscription.updated, andcustomer.subscription.deletedevents, (d) uses anupsertor idempotency key pattern in Supabase to prevent duplicate processing, and (e) returns 200 immediately — any heavy processing is deferred. - Verify and review — run
tsc --noEmitto confirm no TypeScript errors. Invoke/code-reviewon the billing files. Updatedocs/specs/pricing.mdwith any implementation notes. Next step: point to/setup-deploy. Honor the review intensity: underfull, walk through each implementation file for sign-off; underlean, get a single confirmation before writing; undersolo, proceed and summarize after.
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.
- 5d ago First seen · 23 lines · 39 tokens per session scan A e3fe63fc4b97
setup-billing is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 702 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
billing-automation
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.
favcrm-billing-commerce
Use for invoices, payments, products, orders, promotions, subscriptions, overdue follow-up, and commerce operations in FavCRM.
gumroad-support-refund-request
Handle buyer refund requests on Gumroad — standard, subscription, and duplicate-charge cases. Use when a ticket asks for money back, reports a double charge, or a seller is unresponsive to a refund. Decides eligibility, executes, and replies.
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.
stripe
Stripe API integration with managed OAuth. Manage customers, subscriptions, invoices, products, prices, and payments. Use this skill when users want to process payments, manage billing, or handle subscriptions with Stripe. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).…
ai-slop
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside…