billing

A coordinator for iOS subscriptions and in-app purchases, including products sold through Apple’s App Store and RevenueCat, a service that manages subscription data in apps.

In plain words
What is it for?
Use it for product catalog changes, pricing and trial decisions, localization, App Store Connect–RevenueCat checks, and subscription metadata reviews.
Why use it?
It helps keep product identifiers, prices, offers, metadata, and subscription settings aligned across the systems involved in selling an iOS subscription.

Agent for Codex

Install

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.

agentmods
npx agentmods add agents/moasq/ios-dev-agent/billing
Clone the repo
git clone --depth 1 https://github.com/moasq/ios-dev-agent

Made for: Codex.

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 453 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00045 $0.00453
Opus 5 $0.00023 $0.00227
Sonnet 5 $0.00009 $0.00091
Haiku 4.5 $0.00005 $0.00045

Measured yesterday against content hash 08655ac427e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.agents/agents/billing.md · 49 lines

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 asc after catalog state is ready.

Skills

  • business-model
  • billing-finance-calculator
  • paywall
  • paywall-pricing-display
  • asc-revenuecat-catalog-sync
  • asc-subscription-localization
  • asc-ppp-pricing
  • asc-cli-usage
  • revenuecat

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 asc and RevenueCat work to revenuecat with 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.
Changes

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.

  1. yesterday First seen · 49 lines · 45 tokens per session scan A 08655ac427e9

Subscribe to this mod's changes

billing is an agent published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 453 once invoked, about $0.0002 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.