Agent skill · marketing growth · jeremylongshore
alchemy-cost-tuning
Govern Alchemy compute usage and spend with current account evidence, workload attribution, budgets, and reversible optimizations. Use when forecasting or reducing Alchemy cost. Trigger with "Alchemy cost", "Alchemy compute units", or "reduce Alchemy spend".
Why this skill is useful
Provides specific optimization strategies and executable scripts for managing Alchemy API costs that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. Requires alchemy account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Alchemy Usage and Cost Governance Overview Govern Alchemy compute usage and spend with current account evidence, workload attribution, budgets, and reversible optimizations. This workflow produces a reviewable artifact and negative-path evidence before any live side effect. Prerequisites Current first-party Alchemy documentation for the selected product, chain, feature, client, authentication method, limit, and lifecycle. Named product, application, security, data/privacy, budget, release, and operations owners appropriate to the requested scope. Synthetic or approved non-production fixtures, a credential canary, explicit success criteria, and a tested rollback boundary. Current Contract Alchemy pricing plans, included capacity, compute-unit costs, and elastic-demand terms are mutable. Cost decisions use the current account contract, current method-cost documentation, and observed usage—not embedded plan tables. Admin usage access requires an authorized Admin access key or dashboard owner. Authentication Treat billing, application attribution, and usage data as restricted operational data. Keep Admin access keys separate from application keys and never place usage exports or credentials in public repositories. Instructions 1. Record the account, billing window, plan, approved budget, elastic-demand state, currency, owner, and dated source evidence. 2. Attribute observed usage by application, environment, method family, chain, traffic class, and release using the authorized dashboard or Admin usage interface. 3. Reconcile observed compute units and charges to the current contract; label estimates and unattributed usage explicitly. 4. Rank optimizations by correctness risk: remove duplicate calls, cache immutable data, bound pages, batch where documented, schedule background work, and reserve capacity for critical traffic. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/alchemy-cost-tuning