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.
git 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/overview)<a href="https://agentmods.dev/rules/stratokit/strato-db/overview"><img src="https://agentmods.dev/badge/rules/stratokit/strato-db/overview/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/stratokit/strato-db/overview"><img src="https://agentmods.dev/badge/rules/stratokit/strato-db/overview.svg" alt="Reviewed on agentmods" width="80" 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.00855 | $0.00855 |
| Opus 5.5 | $0.00342 | $0.00342 |
| Sonnet 5.5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
Overview 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StratoDB Project Overview
Version: 3.11.0 (from package.json) Description: NoSQL-hybrid with Event Sourcing based on sqlite.
This document provides a high-level overview of the strato-db codebase, intended for AI agent understanding.
Core Concepts
StratoDB is a database system built on SQLite that combines features of NoSQL document stores with the principles of Event Sourcing.
- Document Storage (
JsonModel): Objects are stored in SQLite tables, often with a primary JSON blob column and potentially indexed virtual columns extracted from the JSON structure. - Event Sourcing (
EventSourcingDB,ESModel,EventQueue): Changes to the database state are driven by a sequence of events recorded in a persistent queue (historytable by default). Instead of direct mutation, operations generate events, which are then processed sequentially and atomically to update the database state. - Layered Architecture:
DBModule: Low-level SQLite interaction wrapper (Promises, prepared statements).JsonModelModule: ORM-like layer for interacting with tables as document stores.EventQueueModule: Persistent queue for storing and retrieving events.EventSourcingDBModule: Orchestrates the event processing pipeline, applying events toESModelinstances.ESModelModule: ConnectsJsonModelto the event sourcing system by translating operations into events and providing default event handlers.
Project Structure
.
├── .cursor/rules/ # AI-readable documentation (GENERATED)
│ ├── DB.mdc
│ ├── EventQueue.mdc
│ ├── EventSourcingDB.mdc
│ ├── JsonModel.mdc
│ └── Lib.mdc
├── src/
│ ├── DB/ # Core SQLite wrapper and abstractions
│ ├── EventQueue.js # Event queue implementation
│ ├── EventSourcingDB/ # Event Sourcing orchestration and ESModel
│ ├── JsonModel/ # Document store ORM layer
│ ├── lib/ # Utility functions
│ └── index.js # Main library export
├── dist/ # Compiled output (JS)
├── types.d.ts # Main TypeScript definition file
├── package.json # Project metadata, dependencies, scripts
├── tsconfig.json # TypeScript configuration
├── vite.config.ts # Vite build/test configuration
├── Readme.md # User-facing README
└── ... (config files, tests, etc.)
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.
- 1mo ago First seen · 73 lines · 855 tokens per session scan A e04164311778
Overview is a cursor rule published in the GitHub repository StratoKit/strato-db (14 stars, last pushed 23d ago), licensed MIT. It adds 855 tokens to every session, about $0.0034 per session on Opus 5.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.
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.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.