Rate Limit Guard
v1.0.0Prevent 429 retry loops and wasted tokens. Use before expensive API calls or after hitting rate limits. Enforces preflight checks, backoff, and context shrin...
⭐ 0· 94·0 current·0 all-time
byKairoKid@dodge1218
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the actual instructions. The checks and mitigation steps (concurrency, probes, exponential backoff, context shrinkage) are coherent with a rate-limit guard and no unrelated resources or credentials are requested.
Instruction Scope
SKILL.md contains high-level, scoped runtime guidance (what to check before calls and what to do on 429). It does not instruct reading arbitrary files, contacting external endpoints, or exfiltrating data. It does reference checking 'recent failures' and 'provider/model' which implicitly requires access to the agent's request history/state, but that is expected for this function and is not excessive.
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes risk because nothing is written to disk or downloaded.
Credentials
Requires no environment variables, credentials, or config paths. There is no disproportionate access requested for the stated purpose.
Persistence & Privilege
always is false and the skill is user-invocable. disable-model-invocation is false (normal) which allows autonomous invocation, but that is the platform default and not excessive for this kind of helper.
Assessment
This skill is coherent and low-risk: it only contains runtime guidance and asks for nothing extra. Before installing, consider that the instructions are high-level and rely on the agent's ability to inspect recent request history and manage retries — test it in a safe environment to confirm it behaves as you expect. Also be aware that, while the skill itself requests no credentials, the agent invoking it may have permissions to providers or logs; ensure those agent permissions are appropriate for automated retry/backoff behavior.Like a lobster shell, security has layers — review code before you run it.
agent-intelligencevk97dk1bwbgdbr310jq37vy7m1s84h2kflatestvk97dk1bwbgdbr310jq37vy7m1s84h2kfreliabilityvk97dk1bwbgdbr310jq37vy7m1s84h2kf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.