reviewing-rate-limiting-and-abuse-controls SKILL.md skillA
reviewing-rate-limiting-and-abuse-controls from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/reviewing-rate-limiting-and-abuse-controls@git:20260821.57dfaf1Pins git:20260821.57dfaf1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/reviewing-rate-limiting-and-abuse-controls/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260821.57dfaf1, committed Aug 21, 2026
- Size
- 9,696 bytes
- Repository stars
- 26
- License
- MIT
Review whether sensitive and expensive endpoints are rate-limited and whether the limit can be bypassed, as a coverage-and-keying problem rather than a taint flow. Covers a login, credential-reset, one-time-code verify, signup, token, payment, or expensive-query endpoint with no limit on any layer of its path, a limit keyed on a client-supplied identifier the caller can rotate, a counter held per process so it multiplies across instances, a throttle with no lockout or backoff that permits slow…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Reviewing rate limiting and abuse controls: coverage, keying, and the layer you cannot see Rate limiting is not a taint flow; it is a coverage-and-keying question. For each endpoint where repetition is the attack, guessing a password, brute-forcing a one-time code, enumerating accounts, draining a costly query, three things have to hold: a limit exists somewhere on the path, it is keyed on something the caller cannot rotate, and it counts globally rather than per process. The failures are an endpoint with no limit at all, a limit keyed on a header or field the attacker changes per request to get a fresh bucket, a counter in local memory that multiplies by the number of instances, and a throttle that resets cleanly forever with no lockout. The discipline that makes this review honest is checking every layer, because the enforcement often lives at a gateway the handler never mentions. ## When to use - An endpoint's abuse is repetition: login, credential reset, one-time-code verify, signup, token issuance, payment, invite or message send. - An endpoint is expensive per call: an unbounded search, a report or export, a costly query the caller shapes. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/reviewing-rate-limiting-and-abuse-controls@sha256:8b680793c29cc5e8The line at the top of this page pins the label git:20260821.57dfaf1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3odhfuggwv7bqq3q)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 21, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9696 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3odhfuggwv7bqq3q GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/reviewing-rate-limiting-and-abuse-controls GET https://markdownregistry.com/api/v1/blob/8b680793c29cc5e86127c77582ae001ad032541c10258b213acea4995724134c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.