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/eventsourcingdbgit 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/eventsourcingdb)<a href="https://agentmods.dev/rules/stratokit/strato-db/eventsourcingdb"><img src="https://agentmods.dev/badge/rules/stratokit/strato-db/eventsourcingdb.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.01070 | $0.01070 |
| Opus 5 | $0.00535 | $0.00535 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
EventSourcingDB 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EventSourcingDB & ESModel Modules (src/EventSourcingDB)
These modules implement the core event sourcing pattern for the database.
Core Components
EventSourcingDB.js (EventSourcingDB class)
- Purpose: Orchestrates the event sourcing process. It manages the flow of events from the
EventQueueto theESModelinstances, ensuring atomic and ordered processing. - Key Features:
- Event Loop: Polls or waits for new events from the
EventQueue. - Event Processing Pipeline: For each event:
- Preprocessing: Calls
preprocessorstatic methods on all registeredESModels.ESModel.preprocessorassigns IDs to new objects. - Reduction: Calls
reducerstatic methods on allESModels.ESModel.reducercalculates the necessary change (ins,upd,rm,esFail) based on the event type and current state. - Application: Within a database transaction:
- Calls
applyResult(viamodel.applyResult(result)which calls the importedapplyResult) on each model with its calculated result, making the actual database changes using the underlyingJsonModelmethods (in writable mode). - Calls
derivermethods on models for post-processing (also in writable mode).
- Calls
- Commit: Commits the transaction and updates the database
user_version.
- Preprocessing: Calls
- Sub-events: Handles events dispatched during the processing of another event, processing them recursively within the same transaction.
- Error Handling: Logs errors and halts processing if a reducer or applicator fails. Stores error information in the event's
resultfield in theEventQueue. - State Management: Manages database connections (potentially separate R/W and RO), tracks the current processed version, and uses
AsyncLocalStoragefor context. - Lifecycle Events: Emits events ('begin', 'result', 'error', 'processed') for monitoring.
- Event Loop: Polls or waits for new events from the
- Dependencies:
DB,EventQueue,ESModel,debug,lodash,AsyncLocalStorage.
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 · 63 lines · 1,070 tokens per session scan A e1a4ec03e4ca
EventSourcingDB is a cursor rule published in the GitHub repository StratoKit/strato-db (14 stars, last pushed 6mo ago), licensed MIT. It adds 1,070 tokens to every session, about $0.0053 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
chdb
See CONTRIBUTING.md for the full contributor guide, including the crash-diagnosis rule (always capture the stack trace before changing code on SIGSEGV / SIGABRT / SIGFPE / SIGILL / SIGBUS / SIGSYS).
git-conventions
See CONTRIBUTING.md → "PR & commit conventions" for PR title format, commit messages, and branch naming.
chdb-ds
See AGENTS.md for chdb-ds design and testing principles.
cursorrules
BEFORE making any changes or starting work, ALWAYS.
architect
Global Architect rules for sandraschi's dev environment (Unity and other integrations, FastMCP, React). See mcp-central-docs integrations.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.