request-limit-rule

request-limit-rule is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 48 tokens per session, scanned A, original, MIT.

A request-limit rule that allows each user to make three requests per pool.

In plain words
What is it for?
It helps enforce a limit of three requests per user in each pool.
Why use it?
It prevents one user from sending more than the specified number of requests in a pool.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/request-limit-rule
Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for request-limit-rule

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/request-limit-rule.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/request-limit-rule)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/request-limit-rule"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/request-limit-rule.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 This file is loaded in full into every session.
When invoked 48 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00048
Opus 5 $0.00024 $0.00024
Sonnet 5 $0.00010 $0.00010
Haiku 4.5 $0.00005 $0.00005

Measured 6d ago against content hash 8d5b70410a1a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

request-limit-rule scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

docs/rules/backend/nodejs/express-mongodb/request-limit-rule.mdc · 6 lines

What it actually says

  • 限制每个用户每个池的请求数量为 3 个。
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 6 lines · 48 tokens per session scan A 8d5b70410a1a

Subscribe to this mod's changes

request-limit-rule is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (232 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.