entry-management-rules

entry-management-rules is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 77 tokens per session, scanned A, original, MIT.

Rules for managing entries in a pool, including a limit of three entries per user and numbered entries from 1 to 3.

In plain words
What is it for?
Use it when creating, numbering, limiting, or tracking user entries in a pool.
Why use it?
It prevents too many entries and keeps each entry's selection separate and trackable.

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/entry-management-rules
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 entry-management-rules

README.md
[![agentmods](https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/entry-management-rules.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/entry-management-rules)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/entry-management-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/entry-management-rules.svg" alt="Measured on agentmods" height="20"></a>
Per session 77 This file is loaded in full into every session.
When invoked 77 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.00077 $0.00077
Opus 5 $0.00039 $0.00039
Sonnet 5 $0.00015 $0.00015
Haiku 4.5 $0.00008 $0.00008

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

Security

Grade A, and why

entry-management-rules 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/entry-management-rules.mdc · 8 lines

What it actually says

  • 每个用户每个池最多可以有 3 个条目。
  • 条目编号为 1、2、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 · 8 lines · 77 tokens per session scan A 4c99e9766616

Subscribe to this mod's changes

entry-management-rules is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (232 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session, about $0.0004 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.