Agent skill · marketing growth · jeremylongshore
ideogram-cost-tuning
Govern Ideogram prepaid spend through admission budgets, route choice, output bounds, useful-result accounting, and cleanup. Use when reducing cost or designing billing controls. Trigger with "cut Ideogram spend", "budget Ideogram generations", or "audit Ideogram API cost".
Why this skill is useful
Provides specific strategies and scripts for optimizing API costs with Ideogram that the AI wouldn't generate on its own.
What it needs
Requires bash, curl, grep installed locally. Requires ideogram account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Cost Governance Overview Control prepaid Ideogram consumption without embedding prices that can drift. Tie admission to an accountable budget, choose the narrowest route, bound outputs and retries, and measure durable safe results rather than HTTP success or generated candidates. Prerequisites Team billing owner, current balance source, budget period, workload owner, and quality floor. Request volume, endpoint and rendering mix, output count, retry rate, unsafe rate, and storage failures. A current pricing review from the first-party API pricing page. Current Contract Ideogram API billing is separate from the web application, requires positive prepaid credit, and can use auto-recharge. Keys in one team share credits and billing, so per-key usage is not a separate vendor balance. Prices and recharge choices are time-sensitive and must be verified rather than copied into this skill. Authentication Workers use server-side IDEOGRAMAPIKEY as Api-Key to https://api.ideogram.ai. Cost evidence may include team, endpoint, request, and opaque generation identifiers, but not the key, prompts, images, or URLs. Instructions 1. Retrieve current first-party pricing and balance behavior, recording date, currency, unit, and owner. 2. Inventory demand by tenant, use case, route, rendering option, output count, retry class, safety result, and durable-storage result. 3. Define request, tenant, daily, campaign, and incident ceilings with fail-closed admission. 4. Choose the least costly route that still meets model, quality, transparency, edit, or tool requirements. 5. Prevent duplicate paid work by persisting async identifiers, bounding retries, expiring stale queue items, and deduplicating callers. 6. Attribute spend to useful safe assets that reached durable storage; surface unsafe, failed, abandoned, and expired-URL waste separately. 7. Canary each tuning change and retain a quality, safety, latency, and rollback comparison. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-cost-tuning