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 dodopayments/dodo-agent-plugin --skill mobile-checkoutgit clone --depth 1 https://github.com/dodopayments/dodo-agent-pluginWrote 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/dodopayments/dodo-agent-plugin/mobile-checkout)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/mobile-checkout"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/mobile-checkout/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/dodopayments/dodo-agent-plugin/mobile-checkout"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/mobile-checkout.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.00069 | $0.02205 |
| Opus 5.5 | $0.00028 | $0.00882 |
| Sonnet 5.5 | $0.00014 | $0.00441 |
| Haiku 4.5 | $0.00007 | $0.00220 |
Grade A, and why
mobile-checkout 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 19d 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.
This is a copy
100% identical to mobile-checkout — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile In-App Checkout
This skill covers integrating Dodo Payments hosted checkout into native and cross-platform mobile apps using secure system browser contexts.
When to use this skill
- Building a React Native app with Turbo Module checkout integration
- Adding checkout to a Flutter app via native bridge
- Implementing native iOS or Android checkout with secure browser contexts
- Registering custom URL schemes and deep links for payment return
- Handling abandoned checkout sessions and recovery flows
- Confirming payment authority server-side before granting access
Core principle: Backend creates, mobile opens
Your backend creates the checkout session and returns a URL. The mobile app opens that URL in a secure browser context. Your API key must never be embedded in the app binary. The mobile SDK result is informational only; always verify the payment server-side via webhook or API before unlocking features or granting access.
Architecture overview
- Backend: Create a checkout session via
client.checkoutSessions.create(...)and return thecheckout_urlto your mobile app. - Mobile app: Call the platform-specific SDK with the checkout URL and a registered return URL scheme.
- Browser context: The SDK opens the URL in a secure system browser: SFSafariViewController on iOS and Chrome Custom Tabs on Android.
- Return: After payment, the browser navigates to your return URL. The SDK captures the result and passes it to your app.
- Verification: Query the checkout session or listen for a webhook to confirm the payment before granting access.
React Native (Turbo Module)
Full guide: references/react-native.md.
Covers:
- Installation
- Setup
- Starting checkout
- Abandoned session recovery
- Android minSdk requirement
Flutter
Full guide: references/flutter.md.
Covers:
- Installation
- Setup
- Starting checkout
- Return URL registration
iOS (native)
Full guide: references/ios.md.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · -238 lines · +41 tokens per session e75312e41970
- 1mo ago First seen · 522 lines · 28 tokens per session scan A 43b81403dccd
mobile-checkout is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed 16d ago), licensed MIT. It adds 69 tokens to every session and 2,205 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to mobile-checkout, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mobile-checkout
Dodo Payments in-app checkout for React Native, Flutter, native iOS, and Android using SFSafariViewController or Chrome Custom Tabs. Use when a mobile app must open a backend-created checkout session, handle deep link or custom URL scheme returns, recover abandoned checkouts, and verify payment server-side before…
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
google-play
Google Play Developer API (Android Publisher) integration with managed OAuth. Manage apps, subscriptions, in-app purchases, and reviews. Use this skill when users want to interact with Google Play Console programmatically. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
horizon-app-testing
Run or inspect declared iOS and Android native app tests through Horizon devicetestrun and app MCP tools. Use for App Automate sessions, native actions, evidence, and cleanup; desktop fixtures use horizon-device.
gplay-iap-setup
In-app products, subscriptions, base plans, and offers setup for Google Play monetization, including bulk-localizing subscription display names, descriptions, and benefits across all locales. Use when configuring in-app purchases or subscription products.
rc-revenuecat-api-quick-reference
Use this skill as a quick reference for the RevenueCat Android SDK 10.x and REST API. Covers SDK init, common Purchases calls, CustomerInfo / Offerings access patterns, and the most used REST endpoints.