Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/alchemy-cost-tuning

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/alchemy-cost-tuning

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈70 tokens for metadata: the name and description. ≈1k when used: this file. ≈791 more on demand in 1 file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈280 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Forecast base, burst, and failure/retry scenarios with ranges rather than a false point estimate; set budget alerts and an approved response owner.
  6. Canary one change, compare cost and SLO deltas, preserve completeness, and roll back if savings depend on hidden errors or stale data.

Tool Discipline

Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, wallet addresses, customer data, plan changes, spend, key creation or rotation, webhook changes, deployment, replay, transaction construction, signing, broadcast, or deletion.

Approval Boundaries

Finance/budget owner approves plan, capacity, and elastic spend. Product approves freshness or degraded-mode tradeoffs. Security approves Admin API credential use.

Error Handling

  • Do not quote remembered plan allowances or method costs as current facts.
  • Do not reduce cost by hiding partial errors, skipping pagination, or silently serving stale data.
  • If usage cannot be attributed, surface the gap before recommending a plan change.

Output

Return the dated account contract, usage attribution, reconciliation, forecast ranges, optimization register, budget alerts, canary evidence, SLO impact, and approval/rollback decision. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • Attribute a backfill spike to its application and method family, then schedule and cap it without consuming the critical-read reserve.
  • Reject a cache proposal whose apparent savings come from labeling partial Portfolio results complete.

Validation

Exercise and record expected and observed results for:

  • unattributed usage
  • changed method cost
  • burst forecast
  • retry amplification
  • budget threshold
  • optimization rollback

Resources

  • Current first-party evidence map — recheck dated Alchemy sources before execution.
  • Treat observed account, application, network, indexer, chain, or provider behavior as environment-specific evidence, never a universal guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a monitoring tool and optimized client for Alchemy API compute unit usage. While functional and using official SDKs, it processes external blockchain metadata which introduces a potential surface for indirect prompt injection.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<account> <billing-window> <budget>
version
2.0.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "alchemy",
  "cost",
  "governance"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/alchemy-cost-tuning