Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants.

MITAuto-check passedBackend & APIs

Install Alchemy Rate Limits

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-rate-limits -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace alchemy-rate-limits --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/alchemy-rate-limits .claude/skills/alchemy-rate-limits && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
alchemy-rate-limits
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
539 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants.

  • Works in 6 steps: Inventory every workload sharing the… → Recheck current method costs, account… → Create a shared admission budget across… → …
  • Handling rate limits
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Alchemy Rate Limits is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants. Use when preventing or handling rate limits. Trigger with "Alchemy rate limit", "Alchemy throughput", or "fix Alchemy 429s".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval

It sits in Backend & APIs, covering Rate limiting. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Handling rate limits
  • With Alchemy rate limit
  • Alchemy throughput
  • Fix Alchemy 429s

Example prompts

  • “Alchemy rate limit”
  • “Alchemy throughput”
  • “fix Alchemy 429s”
  • “/alchemy-rate-limits”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Inventory every workload sharing the account by method family, estimated current compute-unit cost, burst shape, priority, idempotency…
  2. Recheck current method costs, account throughput, plan terms, and elastic-demand behavior; record source date and observed tenant settings.
  3. Create a shared admission budget across processes, reserve capacity for critical reads, and shed or defer background work before saturation.
  4. Use concurrency limits plus bounded exponential backoff with jitter, honoring provider guidance and retrying only idempotent operations…
  5. Emit attempt count, queue time, response class, observed usage, and final disposition without logging credentials or full user payloads.
  6. Load-test below, at, and above the approved envelope; prove recovery, exhausted-budget behavior, and rollback before changing production…

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval

    From compatibility in the SKILL.md frontmatter.

Context cost

Alchemy Rate Limits loads about 1.3k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 539 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 539 words, ~1,255 tokens.

Download SKILL.mdSave it as .claude/skills/alchemy-rate-limits/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
alchemy-rate-limits
description
Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants. Use when preventing or handling rate limits. Trigger with "Alchemy rate limit", "Alchemy throughput", or "fix Alchemy 429s".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval
argument-hint
<traffic-class> <account> <slo>
version
2.0.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, alchemy, rate-limits, reliability
model
inherit
effort
high

Alchemy Throughput and Backpressure Control

Overview

Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants. 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 throughput is measured in compute units at the account level using a rolling ten-second token-bucket model. Method costs, plan allowances, and elastic behavior can change. A per-process requests-per-second limiter is therefore insufficient: control must use current account terms, method mix, shared consumers, response signals, and measured demand.

Authentication

Usage inspection requires the authorized dashboard owner or an Admin access key for the documented Admin API; an application key is not an Admin credential. Never export account usage or credential material into public logs.

Instructions

  1. Inventory every workload sharing the account by method family, estimated current compute-unit cost, burst shape, priority, idempotency, and SLO.
  2. Recheck current method costs, account throughput, plan terms, and elastic-demand behavior; record source date and observed tenant settings.
  3. Create a shared admission budget across processes, reserve capacity for critical reads, and shed or defer background work before saturation.
  4. Use concurrency limits plus bounded exponential backoff with jitter, honoring provider guidance and retrying only idempotent operations automatically.
  5. Emit attempt count, queue time, response class, observed usage, and final disposition without logging credentials or full user payloads.
  6. Load-test below, at, and above the approved envelope; prove recovery, exhausted-budget behavior, and rollback before changing production limits.

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.

Show full SKILL.md (194 more words)Show less

Approval Boundaries

Operations approves admission and retry policy; product approves degraded behavior. Purchasing capacity, enabling elastic spend, or changing account limits requires budget-owner approval.

Error Handling

  • Do not hardcode remembered free-plan throughput or method costs as a permanent limiter.
  • Do not retry deterministic JSON-RPC errors or non-idempotent writes automatically.
  • If independent processes cannot share a budget, set conservative partitions and document the risk of account-level contention.

Output

Return the workload/CU inventory, dated account assumptions, shared admission design, retry matrix, telemetry, load evidence, spend boundary, degraded behavior, and rollback threshold. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • Reserve throughput for customer reads while deferring a metadata backfill when the shared rolling window approaches its approved envelope.
  • Demonstrate that a repeated 429 stops after the retry budget and returns an explicit degraded result rather than an infinite wait.

Validation

Exercise and record expected and observed results for:

  • short burst
  • sustained saturation
  • shared-worker contention
  • 429 with retry guidance
  • non-idempotent request
  • retry budget exhausted

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.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/alchemy-rate-limits of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Alchemy Rate Limits next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Alchemy Rate Limits compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Alchemy Rate Limits this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Add Hosted Keysimstudioai/sim30k—~3.6kAutomated safety check: PassApache-2.0
Upstash Ratelimit TSupstash/ratelimit-js2k—~313Automated safety check: PassMIT
Repo2skillzhangyanxs/repo2skill246—~3.6kAutomated safety check: PassNone
Better Auth Security Best PracticesEpicenterHQ/epicenter4.8k—~896Automated safety check: PassCustom licence
Dload Fetch Toolphp-internal/dload105—~1.1kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Add Hosted Key

    simstudioai/sim

    Add hosted API key support to a tool so Sim provides the key (metered and billed to the workspace) when a user has not brought their own.

    30k GitHub stars~3.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Upstash Ratelimit TS

    upstash/ratelimit-js

    Official

    Lightweight guidance for using the Redis Rate Limit TypeScript SDK, including setup steps, basic usage, and pointers to advanced algorithm, features, pricing, and traffic‑protection docs.

    2k GitHub stars~313 tokensUpdated 16 days ago
    Backend & APIsAuto-check passed
  • Repo2skill

    zhangyanxs/repo2skill

    Convert GitHub/GitLab/Gitee repositories into comprehensive OpenCode Skills using embedded LLM calls with multiple mirrors and rate limit handling

    246 GitHub stars~3.6k tokensUpdated 7 mo ago
    Backend & APIsAuto-check passed
  • Better Auth security hardening: rate limits, secrets, CSRF, trusted origins, cookies, sessions, OAuth tokens, and audit logging.

    4.8k GitHub stars~896 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • Dload Fetch Tool

    php-internal/dload

    Get a CLI tool — native binary or PHAR — from a GitHub release into a project folder with dload (vendor/bin/dload).

    105 GitHub stars~1.1k tokensUpdated today
    Backend & APIsAuto-check passed
  • API Gateway

    itsmostafa/aws-agent-skills

    AWS API Gateway for REST and HTTP API management. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub stars~2.2k tokensUpdated 5 days ago
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Alchemy Rate Limits

What does Alchemy Rate Limits do?

Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants. Alchemy Rate Limits is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design account-aware Alchemy throttling, bounded retries, and admission control from observed throughput rather than stale plan constants.

When should I use Alchemy Rate Limits?

Alchemy Rate Limits fits situations like: handling rate limits; with Alchemy rate limit; alchemy throughput; fix Alchemy 429s.

How do I install Alchemy Rate Limits in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-rate-limits -a claude-code`. Or copy the skill folder (skills/.curated/alchemy-rate-limits in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/alchemy-rate-limits in your project. Claude Code loads it when a task matches its description.

How do I install Alchemy Rate Limits in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-rate-limits -a codex`. Or copy the skill folder (skills/.curated/alchemy-rate-limits in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/alchemy-rate-limits in your project. Codex loads it when a task matches its description.

Can I use Alchemy Rate Limits in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-rate-limits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/alchemy-rate-limits, .gemini/skills/alchemy-rate-limits, .github/skills/alchemy-rate-limits and .opencode/skills/alchemy-rate-limits in your project.

What does Alchemy Rate Limits need to run?

SKILL.md names no scripts, command-line tools or credentials: Alchemy Rate Limits is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval.

Does Alchemy Rate Limits access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Alchemy Rate Limits safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Alchemy Rate Limits use?

Alchemy Rate Limits is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Alchemy Rate Limits use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 793 tokens, read only when the agent opens those files.

What are the alternatives to Alchemy Rate Limits?

Skills that share tags, products or a category with Alchemy Rate Limits: Add Hosted Key (simstudioai/sim, 30k stars), Upstash Ratelimit TS (upstash/ratelimit-js, 2k stars), Repo2skill (zhangyanxs/repo2skill, 246 stars) and Better Auth Security Best Practices (EpicenterHQ/epicenter, 4.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Alchemy Rate Limits?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.