---
skill_id: gf-po-rate-limit-incident-pack
evaluation: free
quality: agent-decision-grade
functional: true
price_usd_full: 9.99
price_label: $9.99 / unlock
kind: service
category: Agent Ops
challenge: https://lvlltd.com/api/pay?skill=gf-po-rate-limit-incident-pack
outline: https://lvlltd.com/skills/gf-po-rate-limit-incident-pack/outline.json
runtime_after_unlock: src/index.js createSkill
standards: x402, ERC-7857
completion_pass: functional-v1
---

# Free sample — Rate-Limit Incident Pack

**Skill ID:** `gf-po-rate-limit-incident-pack`  
**Unlock:** $9.99 / unlock USDC on Base via x402  
**What you get after pay:** runnable sealed pack (`createSkill().run`) + workbook + templates  

## Summary

Incident pack for rate-limit storms: detection signals, shed vs queue decisions, client backoff, and post-incident budget retune.

When 429s cascade into agent tool storms and user retries, this pack gives commanders a sealed play: detect, shed, communicate, restore, and retune budgets. Free outline first; x402 sealed unlock. Not legal advice; no availability guarantees.

## When to use

- Agent tool-call bursts or bot scrapers trip edge limits and legitimate traffic collapses under synchronized retries.
- On-call lacks a single place that separates edge 429, app budget exhaustion, and upstream provider throttling.
- Post-incident you need a budget retune worksheet instead of permanently raising limits “just in case.”

## Decision-grade outline (free)

1. Detect: map signals for edge 429 rate, app reject codes, agent tool-fail %, queue depth, and retry amplification ratios in the first five minutes.
2. Decide shed vs queue: which routes drop, which enqueue, which require authenticated-only mode, and who approves each lever.
3. Stabilize clients: publish Retry-After, jittered backoff, circuit-breaker guidance for agents, and kill switches for noncritical scrapers.
4. Communicate: status templates for users and internal channels with estimated recovery and known-safe actions during the storm.
5. Retune budgets post-incident: per-IP, per-key, per-tenant, and per-tool limits with evidence of false positives and residual risk.

## Capabilities

- Rate-limit storm first-five-minutes signal map for edge, app, and agent layers
- Shed-versus-queue decision tree with authenticated-only and kill-switch levers
- Client and agent backoff guidance including Retry-After and jitter patterns
- Status and internal comms templates for limit storms
- Post-incident budget retune worksheet tied to measured false positives

## Artifacts after unlock

- `rate-limit-incident-runbook.md`
- `shed-queue-decision-tree.yaml`
- `budget-retune-worksheet.csv`
- `status-comms-templates.md`

## Detailed description

Rate-limit incidents are rarely a single threshold—they are feedback loops. Clients and agents retry in lockstep, queues grow, and someone “fixes” the outage by opening limits forever. The Rate-Limit Incident Pack is an agent-ops reliability service for the moment 429s become a storm. Detection maps distinguish edge rejections, application budget exhaustion, and upstream provider throttling so commanders do not treat every red chart as the same lever. Shed-versus-queue decisions are explicit: which public routes drop first, which authenticated paths enqueue, when to flip authenticated-only mode, and who can enable scraper kill switches. Client stabilization covers Retry-After, jittered exponential backoff, and agent circuit breakers that stop tool storms from eating the remaining budget. Comms templates keep user-facing status honest without inventing recovery ETAs from vibes. After the storm, a budget retune worksheet forces evidence: which limits fired correctly, which false-positived paying users, and which per-tool agent budgets need narrower bursts. A free outline ships with the listing; the sealed pack unlocks via x402 on Base with USDC. Operational guidance only—not legal advice, not a DDoS mitigation product, and it makes no uptime or revenue guarantees. Use it so the next 429 cascade ends with better budgets, not permanent open gates.

## Functional runtime (paid)

After verified payment the sealed pack includes:

| Path | Role |
|------|------|
| `src/index.js` | `createSkill`, `run`, `plan`, `checklist` |
| `src/runbook.js` | Outline-driven steps with done_when |
| `src/tools.js` | Tool schemas for agent registries |
| `WORKBOOK.md` | Human/operator procedure |
| `templates/` | Checklist + artifact shells |
| `schemas/output.schema.json` | Result contract |

### Agent snippet (after unlock)

```js
import { createSkill } from "./src/index.js";
const skill = createSkill({ tenantId: "ops", agentId: "buyer" });
const result = await skill.run({
  goal: "Execute Rate-Limit Incident Pack for my catalog",
  context: { skill_id: "gf-po-rate-limit-incident-pack" },
  dry_run: false,
});
// result.ok, result.steps, result.artifacts
```

## Pay path

1. Free: this sample + outline.json  
2. `GET https://lvlltd.com/api/pay?skill=gf-po-rate-limit-incident-pack` → HTTP 402  
3. Transfer `maxAmountRequired` USDC to `payTo` on Base  
4. `POST /api/pay` with `X-PAYMENT: {"txHash":"0x…","skill":"gf-po-rate-limit-incident-pack"}`  
5. Write `sealed_pack.files` to disk or use install-unlocked-pack.mjs  
6. Re-redeem anytime with the same verified txHash  

## Honesty

- No revenue, conversion, or uptime guarantees  
- Not legal, tax, medical, or investment advice  
- Crypto transfers are irreversible  
- Confirmed unlocks only for proof strips (/api/proof)  

*Public `/sealed/gf-po-rate-limit-incident-pack/` is teaser-only. Full `src/` is paywalled under locked sealed delivery.*