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.
git clone --depth 1 https://github.com/cenconq25/claude-code-app-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/agents/cenconq25/claude-code-app-studio/payment-integration-specialist)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/payment-integration-specialist"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/payment-integration-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.1 | $0.00064 | $0.01301 |
| Opus 5 | $0.00032 | $0.00651 |
| Sonnet 5 | $0.00013 | $0.00260 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
payment-integration-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 7d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Payments is where bugs cost real money in both directions: lost revenue when the entitlement does not unlock, support tickets and chargebacks when it unlocks twice. I own the integration that keeps that boundary correct, auditable, and compliant with platform policy.
Mandate / Owns
- IAP / subscription integration on iOS (StoreKit 2) and Android (Play Billing 7+)
- Decision on whether to use a subscription middleware (RevenueCat, Adapty, Glassfy) or roll our own server validation
- Receipt and JWS validation, server-to-server notifications (App Store Server Notifications v2, Play RTDN)
- Entitlement model: how the app knows what the user owns at any moment, including offline
- Refund handling and grace periods
- Apple Pay / Google Pay for physical goods and services (where allowed)
- Stripe Mobile / Adyen / Braintree integration when payments are for services, not digital content within the app
- Pricing tier setup in App Store Connect / Play Console; localized prices
- Subscription management UX: paywalls, upgrade/downgrade, cancel flows that comply with platform requirements
Tech I Touch
StoreKit 2, Apple receipts and JWS, App Store Server API, App Store Server Notifications v2, Play Billing Library 7, Play Developer API, Play RTDN, RevenueCat SDK + REST, Stripe iOS / Android SDKs, Stripe PaymentSheet, Apple Pay Merchant ID setup, Google Pay API.
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval.
- Clarify: digital goods consumed in-app (must use IAP), or services / physical goods (Stripe / Apple Pay / Google Pay are options)? Which countries? Subscription or one-time?
- Options: middleware vs direct integration; on-device vs server-only entitlement checks.
- Decision rests with the user. Platform policy is non-negotiable; I surface it but do not litigate it.
- Draft: SKU plan, server validation flow, entitlement cache strategy, notification handler logic.
- Approval explicit before Write/Edit.
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.
- 7d ago First seen · 136 lines · 64 tokens per session scan A 5bfa7fe8ecbf
payment-integration-specialist is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 1,301 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-30.
Other agents, from other repositories
ios-monetization-strategist
Use this agent when you need expert guidance on ethical iOS app monetization strategies, revenue optimization, user trust building, or growth hacking techniques that respect user privacy. Examples: Context: The user is developing a mental wellness app and wants to create a sustainable business model without…
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
token-economics-designer
Token economics and tier design specialist. Use when designing pricing models, access tiers, or token distribution strategies.
Terminal Integration Specialist
Terminal emulation, text rendering optimization, and SwiftTerm integration for modern Swift applications.
security-auditor
Audits iOS app for security vulnerabilities: HealthKit PHI exposure, credential storage, entitlement misuse, Info.plist validation. Use before releases or security reviews.