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 agentmods add skills/moasq/ios-dev-agent/business-modelnpx skills add moasq/ios-dev-agent --skill business-modelgit 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/skills/moasq/ios-dev-agent/business-model)<a href="https://agentmods.dev/skills/moasq/ios-dev-agent/business-model"><img src="https://agentmods.dev/badge/skills/moasq/ios-dev-agent/business-model.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 | $0.00145 | $0.01106 |
| Opus 5 | $0.00072 | $0.00553 |
| Sonnet 5 | $0.00029 | $0.00221 |
| Haiku 4.5 | $0.00015 | $0.00111 |
Grade A, and why
business-model 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business model — subscription pricing, trials, paywall strategy
Use this skill when setting or revising the monetization model of an iOS subscription app. It turns "what should we charge?" into a repeatable, evidence-based decision.
Why this exists
Pricing and paywall decisions made by gut are usually wrong, and wrong pricing is the single highest-leverage mistake an indie founder can make. This skill forces the four things that make the decision defensible:
- Audit the real competitive set — actual prices, actual trials, actual free tiers. No vibes.
- Ground every claim in cited data — RevenueCat, Adapty, Superwall, Appfigures, Apple's own docs.
- Obey the Apple Review rules — weekly pricing is legal, but the paywall design that presents it is where rejections happen.
- Write the decision and the reasoning into a file that ships with the repo, so the next person (or future-you) can audit why the numbers are what they are.
When to use
- Before creating the first subscription group in App Store Connect.
- When changing a price point, trial length, trial placement, or free-tier scope.
- When a competitor changes their pricing and the team wants to react.
- When a revenue goal changes and you're re-examining LTV math.
- Before running a paywall A/B test (choose the variants from the framework, not from intuition).
- When App Review rejects the paywall under Guideline 3.1.2 / 3.1.3.
The four-phase workflow
Phase 1 — Competitor audit
Follow reference/competitor-audit.md. Every direct + adjacent competitor, every visible price, every trial, every free tier. Output: a markdown comparison table with citations.
Phase 2 — Economic sanity check
Follow reference/pricing-frameworks.md. Validate the weekly vs monthly vs yearly choice against published benchmark data for the target category. Calculate the "save X%" anchor between weekly and yearly — it's the strongest conversion lever on the paywall.
Phase 3 — Trial strategy
Follow reference/trial-strategy.md. Decide: trial on which plans, how long, offer mode (FREE_TRIAL vs PAY_AS_YOU_GO vs PAY_UP_FRONT), placement (hard paywall vs soft paywall), default plan pre-selection.
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.
- 4d ago First seen · 70 lines · 145 tokens per session scan A 47a5fccd2f62
business-model is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 145 tokens to every session and 1,106 once invoked, about $0.0007 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
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
fixing-accessibility
Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
openclaw-design-audit
Audit OpenClaw frontend code and rendered interfaces for Carapace drift, token misuse, primitive reimplementation, accessibility problems, responsive defects, and off-brand copy. Use for design reviews, compliance checks, or scheduled audit-and-fix workflows.
om-ds-guardian
Design System Guardian for Open Mercato. Use for frontend UI work, design-system compliance reviews, semantic token migration, hardcoded color or typography cleanup, DS-compliant page scaffolding, and common DS violations such as arbitrary text sizes, raw color classes, or missing shared states. Prefer this skill…
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…
a11y-audit
Audit a component for WCAG AA accessibility compliance.