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/dbgit 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/db)<a href="https://agentmods.dev/rules/stratokit/strato-db/db"><img src="https://agentmods.dev/badge/rules/stratokit/strato-db/db.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.00372 | $0.00372 |
| Opus 5 | $0.00186 | $0.00186 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
DB 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.
What it actually says
DB Module (src/DB)
This module provides the core database interaction layer, abstracting the underlying SQLite database.
Core Components
DB.js
- Purpose: Provides a high-level abstraction for database connections and operations. It likely manages connection pooling and simplifies common database tasks.
- Key Features: (To be determined by analyzing the file)
- Dependencies:
SQLite.js,Statement.js
SQLite.js
- Purpose: Wraps the
sqlite3library to provide a more promise-based and potentially enhanced interface for interacting directly with SQLite. - Key Features: (To be determined by analyzing the file)
- Dependencies:
sqlite3,Statement.js
Statement.js
- Purpose: Represents a prepared SQL statement, likely offering methods for binding parameters and executing the statement efficiently.
- Key Features: (To be determined by analyzing the file)
- Dependencies:
sqlite3
Usage
(To be determined by analyzing the code and tests)
Dependencies
sqlite3: The underlying Node.js driver for SQLite.async-sema: Likely used for managing concurrency or locking around database operations.dataloader: Potentially used for batching and caching database reads.debug: Used for logging debug information.lodash: Utility library, potentially used for various data manipulations.
Structure
src/
└── DB/
├── DB.js # High-level DB abstraction
├── DB.test.js
├── SQLite.js # sqlite3 wrapper
├── SQLite.test.ts
├── Statement.js # Prepared statement representation
├── Statement.test.js
└── index.js # Module entry point (re-exports)
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 · 372 tokens per session scan A c64ce074e0f0
DB is a cursor rule published in the GitHub repository StratoKit/strato-db (14 stars, last pushed 6mo ago), licensed MIT. It adds 372 tokens to every session, about $0.0019 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.
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.