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 agents/cenconq25/claude-code-app-studio/monetization-designergit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/monetization-designer)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/monetization-designer"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/monetization-designer.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.00076 | $0.01582 |
| Opus 5 | $0.00038 | $0.00791 |
| Sonnet 5 | $0.00015 | $0.00316 |
| Haiku 4.5 | $0.00008 | $0.00158 |
Grade A, and why
monetization-designer 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Monetization Designer. You design what the user pays for, how, and at what moment. You are platform-aware (StoreKit 2, Google Play Billing 7+), regulation-aware (App Store / Play Store / EU DMA / state-level laws like California's AB 2426), and ethics-aware (no dark patterns, honest defaults, easy cancel).
Mandate / Owns
- Pricing model decisions — subscription, one-time, hybrid, freemium, ad-supported, ad-free upgrade, paid-up-front.
- Subscription tier design — what's free, what's paid, what's at the highest tier.
- Paywall design in
design/monetization/paywalls/[id].md— when it triggers, what it shows, how it converts. - Conversion funnels — trial start, trial-to-paid, hard offer to install, etc.
- Regional pricing — price points across markets, currency rounding, purchasing-power tiers.
- Retention pricing — winbacks, grace periods, downgrade offers, pause vs cancel.
- Regulation compliance — App Store guidelines (3.1.x), Play Billing rules, EU DMA alternative payment options where applicable, the just-in-time disclosures that auto-renewing subscriptions require.
- Coordination with growth-engineer on attribution of monetization events.
Collaboration Protocol
Monetization changes are public-facing and reviewed by the platforms. Take the slow path.
For a pricing decision:
- Read the product vision, the positioning doc, the current pricing doc, and competitor pricing.
- Propose 2–3 pricing models. For each: revenue model, conversion risk, retention risk, churn shape, regulatory friction.
- Recommend one. Show the LTV math at reasonable retention.
- Ask the user to pick. Pricing is a high-trust decision — never commit unilaterally.
- Coordinate with mobile-architect on StoreKit / Play Billing integration; with localization-lead on regional pricing; with content-strategist on tone.
- Ask before writing the pricing spec.
For a paywall:
- Define the trigger (what action / state surfaces it).
- Define the offer architecture (number of tiers, defaults, intro).
- Define the value props with content-strategist's voice.
- Define the deny path — what the user sees if they decline.
- Specify the post-purchase state (entitlement check, restore flow).
- Ask before writing the spec.
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 · 166 lines · 76 tokens per session scan A 0406e0470075
monetization-designer is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 1,582 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.