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 skills add vmobifystudio/app-dev-team --skill business-modelgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/business-model)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/business-model"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/business-model/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/skills/vmobifystudio/app-dev-team/business-model"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/business-model.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.00071 | $0.00607 |
| Opus 5.5 | $0.00028 | $0.00243 |
| Sonnet 5.5 | $0.00014 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00061 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business model
The output of this skill is a decision with its arithmetic written down, not a strategy essay. The arithmetic is what makes it possible to be wrong on purpose and notice later.
Pick the model before the price
| Model | Fits when | The thing that kills it |
|---|---|---|
| Paid up front | the value is obvious before use | no trial means no conversion signal at all |
| Freemium → subscription | value compounds with use | the free tier is either useless or sufficient |
| Consumable / credits | usage is bursty and costs you per unit | users cannot predict their spend and stop |
| Ads | reach is large and session length is real | ad load destroys the experience that earned the reach |
| Ads + removal IAP | both of the above | the paid tier competes with your own ad revenue |
The studio's defaults and hard rules live in knowledge/monetization.md (house-conventions) —
NO-AD zones, consent, frequency caps. Those are not negotiable by a pricing decision.
The arithmetic, written out
State each number, and say where it came from — measured, comparable, or assumed:
Price point <value> in <currency/tier>
Cost to serve one user <infra + per-unit + store commission>
Conversion assumption <%> (source: measured | comparable | ASSUMED)
Retention assumption <month-1 / month-12> (source: ...)
Revenue per install price × conversion × expected periods
Break-even installs fixed cost ÷ revenue per install
Every ASSUMED is a hypothesis with a falsifying test, handed to data-analyst to instrument
(growth-analysis). An assumption that is never instrumented is a number that will be quoted for
years as if it were measured — the most expensive artifact this skill can produce.
The trial and the paywall
Decide and record: what is free forever, what the trial includes, its length, whether a card is
required, what happens at expiry to data created during the trial (it must not disappear), and where
the paywall appears in docs/12-flows.md. A paywall not in the flow doc is a paywall QA never tests.
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 · 51 lines · 71 tokens per session scan A 3294d6ce18bd
business-model is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 607 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
ramp
Fetch and follow Ramp's published agent playbooks inside Paperclip, with mandatory approval gates for spend, incorporation, cards, account setup, and other financial actions.
cost
Deep cost exploration and transparency. Shows real token usage, session costs, campaign spend, burn rates, and model breakdown. Reads Claude Code's native session data for exact numbers. Complements /dashboard with focused cost views.
execute-task
Implement one task (or a cohesion bundle) from a signed-off spec (Ready or Active): recompute the execution freshness gate, write the verifying test first, implement to green, run the project's full CI with adaptive retry, converge via the stepsconvergence list (default /polish --nested), then open a draft PR…
orchestrate
Advance one planwright spec by one step: pick the next ready unit critical-path-first (or a cohesion bundle), run the freshness gate, record the dispatch under the per-spec lock, and dispatch /execute-task via the backend. A stateless, disposable orchestrator session; a reconcile sweep rebuilds from disk. Never…
spec-kickoff
Walk a spec bundle section by section to mutual understanding, producing the signed-off kickoff brief downstream skills execute from. On sign-off: runs the Discovery-Rigor lens pass, flips Draft to Ready, records the sign-off record (anchor last), commits, pushes, opens a draft PR, then on clean completion marks the…
tower
The front door: a standing conversational session that takes any ask about the repository in plain language, answers questions, and routes work that changes the repository per request onto visual flight (an isolated worker that lands a draft PR) or instrument flight (the spec pipeline), stating its grounds, with…