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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreGameDev-Claude-CodeWrote 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/commands/hermeticormus/libregamedev-claude-code/monetize)<a href="https://agentmods.dev/commands/hermeticormus/libregamedev-claude-code/monetize"><img src="https://agentmods.dev/badge/commands/hermeticormus/libregamedev-claude-code/monetize/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/commands/hermeticormus/libregamedev-claude-code/monetize"><img src="https://agentmods.dev/badge/commands/hermeticormus/libregamedev-claude-code/monetize.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.00016 | $0.00709 |
| Opus 5.5 | $0.00006 | $0.00284 |
| Sonnet 5.5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
monetize 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 15d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/monetize
Ethical game monetization design, dark pattern auditing, IAP implementation, and player spending protection.
Trigger
/monetize [action] [target]
Actions
design
Design an ethical monetization model for a game.
/monetize design "free-to-play mobile RPG, target: casual players"
/monetize design "indie premium game with optional DLC"
/monetize design "seasonal battle pass for action game"
Output: Model recommendation with ethical rationale, revenue projection considerations, player experience impact.
audit
Evaluate existing monetization design against dark pattern checklist.
/monetize audit "our loot box system with premium currency"
/monetize audit "battle pass design with 100 tiers"
/monetize audit "limited-time offer countdown timers"
Output: Full 20-point ethics checklist, flagged dark patterns, ethical redesign recommendations.
implement
Generate IAP integration code for platform-specific store.
/monetize implement "Steam microtransaction for cosmetics store"
/monetize implement "Google Play Billing for Android IAP"
/monetize implement "Apple StoreKit 2 for iOS subscriptions"
Output: Platform IAP code, receipt validation pattern, purchase confirmation UI with ethical requirements.
test
Add player protections and spending analytics.
/monetize test "voluntary monthly spending cap for players"
/monetize test "parental control spending limit integration"
/monetize test "purchase analytics without exploitative profiling"
Output: SpendingLimits class, platform parental control API integration, analytics schema.
Examples
Evaluating a battle pass:
/monetize audit "battle pass with 100 tiers, top tiers include stat-boosting equipment"
Result: FAILS audit. Items on paid track include stat bonuses = pay-to-win. Redesign: stat items moved to free track or removed; paid track gets cosmetics only.
Designing ethical F2P:
/monetize design "free-to-play action RPG, need revenue from mobile"
Produces: Cosmetics-only store recommendation, premium battle pass design with daily XP calculation showing completion at <90 min/day, optional "supporter pack" DLC for dedicated fans, IAP confirmation flow with mandatory real price display.
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.
- 15d ago First seen · 91 lines · 16 tokens per session scan A a6baef88e8fe
monetize is a command published in the GitHub repository HermeticOrmus/LibreGameDev-Claude-Code (5 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 709 once invoked, about $0.0001 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-10-01.
Other commands, from other repositories
build-and-compilation
These commands drive the build/compile/test dev loop, plus build configuration: triggering Player builds and reading the resulting BuildReport, switching the active build target, enumerating targets, reading/writing EditorUserBuildSettings, and listing Build Profiles. Several commands are asynchronous: trigger the…
animation
Author animation assets: AnimationClips (and their float curves), AnimatorControllers (parameters, layers, states, transitions), and Timeline assets. Create commands write under the authoring root and follow the shared confirm/dryrun convention.
assets-and-files
Commands for creating, importing, moving, copying, renaming, deleting and finding project assets, plus folder and text-file operations. Every agent-supplied path is funnelled through the authoring-root sandbox (it rejects ../ and out-of-project writes); destructive or overwriting operations require confirm=true and…
gameobjects-and-components
Commands for creating GameObjects, querying the scene hierarchy, mutating the core GameObject/Transform surface, and adding/removing components and editing their serialized properties. Scene mutations are wrapped in Unity's Undo system (so a multi-step action reverts as one collapsible step) and are blocked during…
project-settings
Read and change a representative slice of Unity's project-wide settings (Audio, Graphics, Input, Physics, Player, Quality, Tags & Layers, Time). get commands read a group's current values into a ProjectSettingsResponse; set commands mutate them through the shared confirm/dryrun convention, so confirm=true is required…
baking
Bake and clear precomputed scene data: lightmaps, NavMesh, and occlusion culling. Each bake runs asynchronously (returns immediately) — poll the matching bakestatus until completed. The clear commands are destructive and require confirm=true. The getsettings / setsettings pairs read and tune the bake parameters.