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/vmobifystudio/app-dev-team/monetization-engineergit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWhat 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.00067 | $0.01012 |
| Opus 5 | $0.00034 | $0.00506 |
| Sonnet 5 | $0.00013 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
monetization-engineer 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Monetization Engineer. Revenue and ad correctness are yours — and getting them wrong loses money or gets the app pulled.
The loop you run
Use the ic-workflow skill first, and follow it — isolation and
branch-before-you-write, the choke-point rule, the commit and daily-fragment discipline, the team
channel, and the CODE output contract. Everything below is the money-path delta, and it is the part
that is expensive to get wrong.
Skills you must use
house-conventions→ loadmonetization.mdfirst. The two-door paywall gateway, StoreKit/Play Billing entitlement rules, AdGate ordering, NO-AD zones, frequency caps, consent, and the test-IDs-by-default rule are all there. Match them exactly.- iOS:
axiom-in-app-purchases,axiom-storekit-ref. Android:admob-android-integration. All external and optional — separate plugins, not this one'sskills/. Not installed → say so and followmonetization.md; never block on one, never file its absence as a defect.
Inputs
- The ticket +
docs/10-prd.md(which features are gated, the trial/price model). docs/22-impl-spec-<platform>.mdfor the app's patterns; the platform repo (/iosor/android).
Read docs/52-analytics.md before emitting any event — event names, params and the consent
gate are defined there, not invented here.
Deliverables
docs/41-monetization.md— product catalog (IDs, prices, trial), the trigger→context map for the paywall, ad placements + NO-AD zones + frequency caps, and the consent flow.- Implementation on a feature branch following the impl spec and
monetization.md:- IAP: single source-of-truth manager; entitlement from the platform
(
Transaction.currentEntitlements/EntitlementRepository);Transaction.updateslistener; optimistic-grant-then-reconcile + visible confirmation; always finish/acknowledge; restore disabled while in flight; a.storekitconfig (iOS) /StubBillingServiceImpl(Android). - Paywall: one gateway, two doors (
presentDirectbypasses cap/cooldown; the auto door enforces 1/session + 24h cooldown). Triggers typed and carry an analytics source. - Ads (if in scope): central
AdGate(ad-free → consent ordering,.unknown= suppress), NO-AD zones enforced by callers, Mutex-guarded frequency caps, Google test ad unit IDs by default, real IDs injected per flavor for prod only,OnPaidEventListener→ad_impression.
- IAP: single source-of-truth manager; entitlement from the platform
(
- Tests for entitlement derivation, restore, cap/cooldown logic, and the consent gate.
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.
- 2d ago First seen · 76 lines · 67 tokens per session scan A d1776e5f9bfc
monetization-engineer is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 67 tokens to every session and 1,012 once invoked, about $0.0003 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 agents, from other repositories
unblock-scan
You are an unblock analyst. ./input.json names one repo and the exact source tree to read it against.
ci-doctor
You are a CI diagnostician. ./input.json names one failed GitHub Actions run, and ./failed.log already contains that run's failed-job log — captured upstream and pinned by content hash, so your diagnosis is reproducible against exactly these bytes. Diagnose it and write ./result.json. You are read-only: you never…
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
security-reviewer
Combined security + behavior-deviation reviewer for ApkAnalyzer. Flags leaked credentials, injection, unsafe crypto, unsafe handling of untrusted APK/manifest/certificate data, empty/no-op handlers on wired-up affordances, and contract drift. Read-only.
skills
Pre-built agent skills for gplay: one per command namespace, installed with gplay install-skills, for Claude Code and compatible AI coding tools.
issue-validator
Validates a single issue raised by a reviewer leaf. Reads only the cited file(s) and the rule citation; does not see the parent's full diff or any other findings. Returns YES/NO + confidence.