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.
npx agentmods add rules/stratokit/strato-db/eventqueuegit clone --depth 1 https://github.com/StratoKit/strato-dbWrote 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.
[](https://agentmods.dev/rules/stratokit/strato-db/eventqueue)<a href="https://agentmods.dev/rules/stratokit/strato-db/eventqueue"><img src="https://agentmods.dev/badge/rules/stratokit/strato-db/eventqueue.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00511 | $0.00511 |
| Opus 5 | $0.00255 | $0.00255 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
EventQueue 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EventQueue Module (src/EventQueue.js)
This module provides an event queue implementation, likely used for the event sourcing mechanism.
Core Components
EventQueue.js
- Purpose: Implements a persistent event queue backed by a SQLite table (defaulting to
history). It extendsJsonModel, suggesting it leverages the JSON storage capabilities. - Key Features:
- Stores events with
v(auto-incrementing version/ID),type,ts(timestamp),data(JSON),result(JSON), andsize(calculated size of data/result). - Provides methods for adding events (
add), retrieving the latest version (getMaxV), and fetching the next event after a specific version (getNext), including waiting for new events. - Includes database migrations for adding indices and helper views (
_recentHistory,_historyTypes). - Manages internal state (
currentV,knownV) for optimization. - Uses
debugfor logging. - Handles concurrency within the same process using Promises (
_addP). - Optionally keeps the Node.js process alive while waiting (
forever: true). - Allows customization of table name and columns.
- Stores events with
- Dependencies:
JsonModel,debug
Usage
- Instantiate
EventQueue(likely vianew EventQueueImpl(...)although the export might simplify this). - Use
add(type, data, [ts])to append new events. - Use
getMaxV()to get the highest event version number. - Use
getNext(v, [noWait])to retrieve events sequentially, potentially waiting for new ones.
Schema (Default history table)
v: INTEGER PRIMARY KEY AUTOINCREMENT (Event version/ID)type: TEXT (Event type identifier)ts: INTEGER (Timestamp in milliseconds since epoch, indexed)data: JSON (Payload of the event)result: JSON (Result associated with processing the event, optional)size: INTEGER (Calculated size ofdata+resultJSON strings)
Dependencies
debug: Used for logging.JsonModel: Base class providing JSON handling and DB interaction.
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.
- yesterday First seen · 50 lines · 511 tokens per session scan A e7e4555cd6b5
EventQueue is a cursor rule published in the GitHub repository StratoKit/strato-db (14 stars, last pushed 6mo ago), licensed MIT. It adds 511 tokens to every session, about $0.0026 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-04.
Other cursor rules, from other repositories
git-conventions
See CONTRIBUTING.md → "PR & commit conventions" for PR title format, commit messages, and branch naming.
trigger
Postgres Trigger 撰寫規範.
rulesforconvex
description: Convex guidelines globs: alwaysApply: true.
startup-migration-bounded-work
Production djangostartup migrate must be bounded; never run makemigrations in production.
redis_rate_limiting
Complete guide for implementing Redis-based rate limiting with authentication troubleshooting and FastAPI integration.
nodejs-mongodb-jwt-express-react-cursorrules-promp
Cursor rules for Node.js development with MongoDB, JWT, Express, and React integration.