Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Purchasely/Purchasely-AI-Pluginnpx agentmods add skills/purchasely/purchasely-ai-plugin/purchasely-integrateWrote 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/purchasely/purchasely-ai-plugin/purchasely-integrate)<a href="https://agentmods.dev/skills/purchasely/purchasely-ai-plugin/purchasely-integrate"><img src="https://agentmods.dev/badge/skills/purchasely/purchasely-ai-plugin/purchasely-integrate/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/purchasely/purchasely-ai-plugin/purchasely-integrate"><img src="https://agentmods.dev/badge/skills/purchasely/purchasely-ai-plugin/purchasely-integrate.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.00052 | $0.17572 |
| Opus 5 | $0.00026 | $0.08786 |
| Sonnet 5 | $0.00010 | $0.03514 |
| Haiku 4.5 | $0.00005 | $0.01757 |
Grade A, and why
purchasely-integrate 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 8d 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 — 1,236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purchasely SDK Integration Guide
You are guiding a developer through integrating the Purchasely SDK into their mobile app. You must write actual code into the user's project — not just explain what to do.
Reference documentation is available in the ../../references/ directory of this plugin. Before integrating, read ../../references/purchasely-architecture.md to understand the end-to-end platform (SDK ↔ Purchasely Server ↔ stores ↔ your backend ↔ third-party tools) and the Full-mode purchase flow. If the app already sells subscriptions on the web (Stripe, another subscription platform, in-house billing), also read ../../references/cross-platform-subscriptions.md — Purchasely accepts S2S Stripe receipts and the coexistence model has subtle defaults to know about.
The bundled references are intentionally curated, not a full copy of the public docs. If a required integration detail is missing, looks stale, or depends on an exact SDK signature / current Console behavior, verify it against the official Purchasely documentation at https://docs.purchasely.com/ before writing code.
Universal SDK concepts (apply to every platform — iOS, Android, React Native, Flutter, Cordova) are in ../../references/concepts/. Load them as needed:
../../references/concepts/running-modes.md— Full vs Observer modes, log levels../../references/concepts/paywall-actions.md—PLYPresentationActionenum, interceptorproceed/processActionrules../../references/concepts/presentation-types.md— presentation type guard (NORMAL / FALLBACK / DEACTIVATED / CLIENT)../../references/concepts/presentation-cache.md— App-side cache + preload pattern (fetch ahead, display instantly)../../references/concepts/observer-mode-post-purchase.md—proceed/processAction → dismissordering, chaining follow-up placements../../references/concepts/programmatic-purchases.md— Exact app-side purchase APIs by platform../../references/concepts/user-attributes-targeting.md— Audience targeting attributes../../references/concepts/privacy-settings.md—revokeDataProcessingConsent, essential/optional processing, GDPR/CMP choices../../references/concepts/user-identity.md—userLogin/userLogouttiming + anonymous→logged-in merge../../references/concepts/subscription-checks.md— Gating premium content viauserSubscriptions, restore purchases../../references/concepts/subscription-management.md— Opening the native Manage Subscription page (App Store / Play Store)../../references/concepts/promotional-offers.md— Offer types, Apple promotional offers, Google developer-determined offers, offer codes../../references/concepts/campaigns.md— No-code automations (trigger/placement-based),allowDeeplink/allowCampaigns, trigger/deeplink display readiness, use cases../../references/concepts/lottie-animations.md— Lottie animations in Screens (iOS / Android weak dependency bridge; cross-platform host projects)../../references/concepts/analytics-integration.md— Forwarding UI events to Firebase / Amplitude / AppsFlyer + recommended analytics wrapper pattern
Platform-specific deep dives (load the one(s) matching the project's platform — they hold the authoritative install snippets, init signatures, and platform-only patterns):
../../references/ios/initialization.md— iOS install (CocoaPods / SPM / Carthage),Purchasely.start(...)signature, App Tracking Transparency hook order, StoreKit 2 setup../../references/ios/api-reference.md— full iOS API surface with signatures (init, fetch, present, attributes, login, sync, errors)../../references/ios/common-patterns.md— SwiftUI lifecycle, UIKit container embedding,@MainActorrules, presentation cache implementation../../references/android/initialization.md— Android install (Maven Central, store dependencies, ProGuard/R8 rules),Purchasely.Buildersetup../../references/android/api-reference.md— full Android API surface with Kotlin/Java signatures../../references/android/common-patterns.md— Jetpack Compose embedding, Fragment vs View, lifecycle-aware patterns../../references/react-native/integration.md— RN-specific install, Metro setup, plugin alignment, store package../../references/flutter/integration.md— Flutter-specific install, MethodChannel/EventChannel bridge, plugin alignment../../references/cordova/integration.md— Cordova-specific install, plugin add, store plugin, JS callbacks
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.
- 8d ago First seen · 1,236 lines · 52 tokens per session scan A 92bc2d886116
purchasely-integrate is a skill published in the GitHub repository Purchasely/Purchasely-AI-Plugin (2 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 17,572 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-31.
Other skills, from other repositories
play-billing-library-version-upgrade
Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
axiom-implement-iap
Use when the user wants to add in-app purchases, implement StoreKit 2, or set up subscriptions.
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).
subscription-lifecycle
Generates StoreKit 2 subscription lifecycle management — grace periods, billing retry, offer codes, win-back offers, upgrade/downgrade paths, and subscription status monitoring. Use when user needs post-purchase subscription state handling beyond the initial paywall.
subscription-offers
Generates StoreKit 2 code for all subscription offer types — introductory, promotional, offer codes, and win-back. Includes eligibility checks, offer presentation, and the preferredSubscriptionOffer modifier. Use when adding subscription offers, free trials, or promotional pricing.