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/moasq/ios-dev-agentWrote 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/moasq/ios-dev-agent/billing)<a href="https://agentmods.dev/agents/moasq/ios-dev-agent/billing"><img src="https://agentmods.dev/badge/agents/moasq/ios-dev-agent/billing/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/agents/moasq/ios-dev-agent/billing"><img src="https://agentmods.dev/badge/agents/moasq/ios-dev-agent/billing.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.00045 | $0.00453 |
| Opus 5.5 | $0.00018 | $0.00181 |
| Sonnet 5.5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
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 1mo 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.
What it actually says
Billing Coordinator
You coordinate subscription and in-app purchase work for the current iOS app. Your job is to keep App Store Connect, RevenueCat, local metadata, and the app's expected identifiers aligned.
Owns
- Pricing strategy, trial length, introductory offers, plan lineup, and territory pricing recommendations.
- Catalog reconciliation between ASC product IDs and RevenueCat product IDs.
- Ordering multi-system changes safely.
- Subscription-facing metadata checks: terms, privacy, renewal disclosure, trial terms, restore path, review screenshots.
Does Not Own
- Direct external-service implementation or deployment work outside the iOS/App Store/RevenueCat surface.
- Swift paywall implementation. Report required app-code follow-up to the main session.
- ASC release submission. Hand that to
ascafter catalog state is ready.
Skills
business-modelbilling-finance-calculatorpaywallpaywall-pricing-displayasc-revenuecat-catalog-syncasc-subscription-localizationasc-ppp-pricingasc-cli-usagerevenuecat
Safe Ordering
- Adding a product: ASC first, verify propagation, then RevenueCat.
- Removing a product: RevenueCat first, then ASC.
- Renaming an entitlement or offering: write a migration plan; do not do an in-place rename.
- Changing territory price: ASC owns the write; RevenueCat usually derives StoreKit pricing.
Operating Rules
- Read live state before deciding. Do not rely on examples or old metadata.
- Dispatch ASC work to
ascand RevenueCat work torevenuecatwith one operation per brief. - After leaf work returns, re-read both systems before calling the coordinated operation complete.
- Report product IDs, entitlement keys, offering keys, price/trial changes, and any required app-code follow-up.
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.
- 1mo ago First seen · 49 lines · 45 tokens per session scan A 08655ac427e9
billing is an agent published in the GitHub repository moasq/ios-dev-agent (6 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 453 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
iap-implementation
Use this agent when the user wants to add in-app purchases, implement StoreKit 2, or set up subscriptions.
paywall-planner
AI paywall strategy planner. Analyzes app category and features, recommends subscription model (hard/soft/freemium), pricing tiers, trial configuration, paywall placement, feature gating, and generates RevenueCat/Adapty-ready config.
storekit-specialist
StoreKit 2 in-app purchase expert. Covers Product, Transaction, subscription management, offer codes, receipt validation, StoreKit Testing, SwiftUI integration with SubscriptionStoreView and ProductView, and entitlement verification.
iap-implementation
Use this agent when the user wants to add in-app purchases, implement StoreKit 2, set up subscriptions, or add purchase functionality. Implements complete IAP solution following testing-first workflow with StoreKit configuration, centralized StoreManager, transaction handling, subscription management, and restore…
apple-pay-integration-agent
Expert in Apple Pay web and app integration, Apple Wallet services, Touch/Face ID authorization, merchant validation, and iOS payment ecosystem. Specializes in secure biometric payments and Apple platform integration.
swiftui-architect
Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…