- Home
- Skills
- Agents & Orchestration
- Rate Limit Contract Repair
More screenshots
Works with the AI Agents you already use
Rate Limit Contract Repair
Repair rate-limit contract drift in a repository using Cursor.
$1
Rate Limit Contract Repair
Example session with this skill installed
Middleware uses 50 req/min but docs say 100. The SDK retries 429s immediately. Align the repo contract and add tests using the existing fake-clock utility. Do not touch production.
- Read your context and instructions
- Compiled the rate limit contract
Repair decision
RATE-LIMIT CONTRACT DRIFT FOUND. I have centralized the quota in config/limits.ts, updated the SDK to honor Retry-After, and added 12 deterministic tests. Deployed behavior remains unverified.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Rate limit behavior often drifts across repository middleware, route overrides, and public documentation. This leads to client retry storms, broken SDKs, and inconsistent API enforcement that is difficult to debug without production access.
What it does
- Identifies conflicting quotas, windows, and identities across source code, OpenAPI specs, and docs.
- Traces enforcement paths from identity extraction to response serialization and header handling.
- Standardizes 429 response schemas, Retry-After headers, and SDK retry logic.
- Generates safe repository patches to centralize magic numbers and unify policy definitions.
- Provides a deterministic test matrix using fake clocks and mocked adapters for local verification.
Frameworks & tools
Compatible with any repository containing Express, FastAPI, TypeScript, Python, OpenAPI, GraphQL, or standard HTTP client SDKs.
Why this beats prompting it yourself
Manual review misses the subtle drift between a middleware default and a hard-coded route override. This skill enforces a strict contract register that captures every source of truth, ensuring your patches are reviewable and tests are truly deterministic.
Use cases
- Aligning middleware quotas with OpenAPI specifications and public documentation.
- Fixing SDKs that retry unsafe mutations or ignore Retry-After headers.
- Unifying mixed rate-limit identities like user-based vs tenant-based scopes.
- Standardizing response formats across different service mocks and test suites.
Known limitations
Cannot access live Redis instances, production gateways, or real customer traffic logs. It does not perform production migrations or verify deployed quotas.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
No access to live Redis, production gateways, or customer data. Cannot verify deployed behavior or perform database migrations. Requires repository-based evidence for all findings.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 months ago
- Software
Python
Permissions
Permissions are limited to the active local workspace and are used to inspect user-supplied or local workspace files; create or modify bounded local fixes, tests, documentation, or review artifacts; run repository-supported local tests, checks, builds, or parsing commands. The skill package does not require bundled credentials, unrestricted external network access, or automatic production changes.