event

A set of rules for application events, messages that let one part of a program notify other parts that something happened. The example is updating related information after a user's details change.

In plain words
What is it for?
Use it when adding event listeners or triggering follow-up updates after application data changes.
Why use it?
It lets related work listen for changes instead of tightly coupling every operation to the code that caused the change.

Cursor rule for Cursor

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/cool-team-official/cool-admin-midway/event
Clone the repo
git clone --depth 1 https://github.com/cool-team-official/cool-admin-midway

Made for: Cursor.

Per session 3 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 579 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00003 $0.00579
Opus 5 $0.00002 $0.00290
Sonnet 5 $0.00001 $0.00116
Haiku 4.5 $0.00000 $0.00058

Measured today against content hash 84447b9fb8d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

event 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 today.

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.

.cursor/rules/event.mdc · 103 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. today First seen · 103 lines · 3 tokens per session scan A 84447b9fb8d0

Subscribe to this mod's changes

event is a cursor rule published in the GitHub repository cool-team-official/cool-admin-midway (3,266 stars, last pushed 1mo ago), with no licence file. It adds 3 tokens to every session and 579 once invoked, about $0.0000 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-09-01.