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 kensaurus/cursor-kenji --skill audit-monetization-iapgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/audit-monetization-iap)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-monetization-iap"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-monetization-iap.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.00075 | $0.01261 |
| Opus 5 | $0.00037 | $0.00630 |
| Sonnet 5 | $0.00015 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
audit-monetization-iap 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-monetization-iap — Store billing & entitlements
Degree of freedom: MIXED — Phases 0–1 [HIGH freedom]; Phase 2 sandbox
[LOW freedom — run exactly]. Never test against real billing.
Read-only. Entitlements must match what users paid for: no unlock-without-pay, no paid-but-locked, no double-charge, no lost purchase on reinstall.
The two revenue killers are client-trusted entitlements (piracy) and broken restore (refunds + 1-star reviews).
Present findings. Do not patch store/server code until approved. Never test against real billing.
This skill vs neighbors
| Skill | Owns |
|---|---|
| audit-monetization-iap (this) | App Store / Play IAP, restore, store notifications |
audit-payment-system |
Web money-movement, Stripe, ledgers, PCI |
plan-mobile-readiness |
Submission paperwork (IAP via official billing is a checkbox) |
plan-aso |
Store listing conversion, not receipt validation |
plan-privacy-compliance |
Purchase-data in privacy labels |
Do not fire for "Stripe webhook / double charge on the website" →
audit-payment-system.
How to reason
- Observe — quote where "is Pro?" is decided and whether a receipt/token is verified server-side
- Interpret — can a client lie, or can a paid user lose access?
- Classify — client-trust / missing restore / lifecycle hole / correct
- Severity — client-trusted entitlement or broken restore = Critical
Worked example
Observe:
isProreadsRevenueCat.getCustomerInfo()on-device only; no App Store Server Notification handler. Interpret: a patched client can unlock Pro; refunds never revoke. Classify: client-trust + missing lifecycle sync. Severity: Critical. Finding: entitlements | client-only | Critical |lib/pro.ts:18| verify on server + ASN V2 / RTDN
Phase 0 — Detect the billing setup [HIGH freedom]
- Layer: raw StoreKit 2 / Play Billing, or RevenueCat / Adapty / Glassfy
- Entitlement check: client-only vs server-verified
- Backend store of subscription state vs trust-the-SDK-at-runtime
- Products: consumable, non-consumable, auto-renewing sub, trial / intro
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 · 137 lines · 75 tokens per session scan A 48befa01a072
audit-monetization-iap is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 10d ago), licensed MIT. It adds 75 tokens to every session and 1,261 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-database
Use when syncing real-time data, structuring JSON trees, reading/writing, creating listeners, enabling offline persistence, managing presence, sharding, or writing security rules.
flutter-app-architecture
Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).
generate-images-with-firebase-ai
Use when generating or editing images from Flutter/Dart with Firebase AI Logic and a Gemini image model (Nano Banana), making the first call work, choosing Gemini Developer API vs Vertex AI, hitting quota, billing or App Check failures, getting empty or image-only responses, sending a user photo as input, controlling…