Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计通过

convex-rate-limiter凸速率限制器

Agent Skill

convex-rate-limiter 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

412

周安装

17

GitHub Stars

1

下载量

135
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:convex-rate-limiter(凸速率限制器)
来源仓库:https://github.com/imfa-solutions/skills
仓库路径:skills/convex-rate-limiter
安装命令:
npx skills add https://github.com/imfa-solutions/skills --skill convex-rate-limiter
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/imfa-solutions/skills --skill convex-rate-limiter

简介

Convex Rate Limiter 为 Convex 提供类型安全、事务性、应用层级的速率限制能力。

  • 适用于需要实现请求频率控制、API调用配额管理或防止资源过载的 Convex 后端场景。
  • 通过 npm 安装并注册组件,定义命名速率限制器,支持按分钟、小时或秒级延迟进行配置。
  • 使用时需确认项目是否基于 Convex 架构,并检查权限与依赖兼容性,避免影响现有事务逻辑。
  • convex-rate-limiter 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Convex Rate Limiter

@convex-dev/rate-limiter — Type-safe, transactional, application-level rate limiting for Convex.

Installation

npm install @convex-dev/rate-limiter

Register the component in convex/convex.config.ts:

import { defineApp } from "convex/server";
import rateLimiter from "@convex-dev/rate-limiter/convex.config.js";

const app = defineApp();
app.use(rateLimiter);
export default app;

Setup — Define Named Rate Limits

import { RateLimiter, MINUTE, HOUR, SECOND } from "@convex-dev/rate-limiter";
import { components } from "./_generated/api";

const rateLimiter = new RateLimiter(components.rateLimiter, {
  // Fixed window — hard quota that resets each period
  freeTrialSignUp: { kind: "fixed window", rate: 100, period: HOUR },

  // Token bucket — smooth traffic with burst allowance
  sendMessage: { kind: "token bucket", rate: 10, period: MINUTE, capacity: 3 },

  // Failed login throttle
  failedLogins: { kind: "token bucket", rate: 10, period: HOUR },
});
  • period is in milliseconds (SECOND = 1000, MINUTE = 60000, HOUR = 3600000).
  • Multiple RateLimiter instances allowed; config keys must not overlap.

Strategy Selection

StrategyBehaviorBest for
Token bucketTokens refill continuously; unused tokens accumulate up to capacityUser actions, API calls, LLM tokens — smooth traffic, allow bursts
Fixed windowAll tokens granted at period start; hard reset each periodDaily/hourly quotas, signup caps, hard API limits

Token bucket config:

{ kind: "token bucket", rate: 10, period: MINUTE, capacity: 3 }
// capacity = max burst tokens (optional, defaults to rate)

Fixed window config:

{ kind: "fixed window", rate: 100, period: HOUR }
// start: optional custom epoch; random by default to prevent thundering herd

Core API

limit() — Consume tokens

const { ok, retryAfter } = await rateLimiter.limit(ctx, "sendMessage", {
  key: userId,       // Per-entity key (omit for global limit)
  count: 1,          // Tokens to consume (default 1)
  throws: false,     // Set true to auto-throw ConvexError
});
if (!ok) throw new Error(`Rate limited. Retry in ${Math.ceil(retryAfter / 1000)}s`);

check() — Query without consuming (safe in queries)

const { ok, retryAfter } = await rateLimiter.check(ctx, "sendMessage", {
  key: userId,
});

reset() — Clear a rate limit

await rateLimiter.reset(ctx, "failedLogins", { key: email });

throws: true — Auto-throw pattern

import { isRateLimitError } from "@convex-dev/rate-limiter";

await rateLimiter.limit(ctx, "sendMessage", { key: userId, throws: true });
// Throws ConvexError with data: { kind, name, retryAfter }

Catch with isRateLimitError(error) to inspect .data.retryAfter.

Usage Patterns

Global rate limit (no key)

export const signUp = mutation({
  args: { email: v.string() },
  handler: async (ctx, args) => {
    await rateLimiter.limit(ctx, "freeTrialSignUp", { throws: true });
    await ctx.db.insert("users", { email: args.email });
  },
});

Per-user rate limit

export const sendMessage = mutation({
  args: { text: v.string() },
  handler: async (ctx, args) => {
    const user = await ctx.auth.getUserIdentity();
    await rateLimiter.limit(ctx, "sendMessage", {
      key: user?.subject,
      throws: true,
    });
    await ctx.db.insert("messages", { userId: user?.subject, text: args.text });
  },
});

Failed login throttle with reset on success

export const login = mutation({
  args: { email: v.string(), password: v.string() },
  handler: async (ctx, args) => {
    await rateLimiter.limit(ctx, "failedLogins", {
      key: args.email,
      throws: true,
    });
    const success = await verifyCredentials(ctx, args);
    if (success) {
      await rateLimiter.reset(ctx, "failedLogins", { key: args.email });
    }
    return success;
  },
});

Consume multiple tokens at once

await rateLimiter.limit(ctx, "llmTokens", {
  key: userId,
  count: estimateTokens(prompt),
  throws: true,
});

Critical Rules

  1. Always pass key for per-entity limits. Omitting key makes it a global singleton.
  2. Always surface retryAfter to the client — don't just say "rate limited".
  3. Rate limit changes are transactional — they roll back if the mutation fails.
  4. Use throws: true for cleaner code; catch with isRateLimitError().
  5. Reset wisely — reset on success (e.g., login), never on every request.

Common Pitfalls

// BAD: Global limit when you want per-user
await rateLimiter.limit(ctx, "sendMessage");

// GOOD: Per-user limit
await rateLimiter.limit(ctx, "sendMessage", { key: userId });
// BAD: Ignoring retryAfter
const { ok } = await rateLimiter.limit(ctx, "action");
if (!ok) throw new Error("Rate limited");

// GOOD: Tell user when to retry
const { ok, retryAfter } = await rateLimiter.limit(ctx, "action");
if (!ok) throw new Error(`Wait ${Math.ceil(retryAfter / 1000)} seconds`);

Best Practices Summary

PracticeGuidance
Key designUser ID for per-user, IP for anonymous, team ID for team-wide, composites like ${teamId}:${userId}
CapacityToken bucket: capacity = rate * burst_multiplier. Fixed window: defaults to rate
Start simpleAdd sharding/reservation only when needed
Error handlingUse throws: true + isRateLimitError()
Thundering herdFixed window uses random start by default; add jitter to retry times

Advanced Topics

Common Patterns

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.74%
按下载量换算47

Claude

33.57%
按下载量换算45

Cursor

17.41%
按下载量换算24

Gemini CLI

9.95%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills