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/libgit 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/lib)<a href="https://agentmods.dev/rules/stratokit/strato-db/lib"><img src="https://agentmods.dev/badge/rules/stratokit/strato-db/lib.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.00324 | $0.00324 |
| Opus 5 | $0.00162 | $0.00162 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
Lib 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
Lib Module (src/lib)
This directory contains miscellaneous utility functions used across the codebase.
Core Components
settleAll.js
- Purpose: Provides a function likely analogous to
Promise.allSettled, allowing multiple promises to be awaited, capturing both fulfilled values and rejection reasons without short-circuiting on the first rejection. - Usage: Useful when you need to process a batch of independent asynchronous operations and handle their individual outcomes.
slugify.js
- Purpose: Converts a string into a URL-friendly "slug" format.
- Key Features: Likely removes special characters, converts to lowercase, and replaces spaces with hyphens.
- Usage: Generating clean identifiers for URLs or filenames.
warning.js
- Purpose: Handles the display of warnings or deprecation notices, potentially only in development environments.
- Key Features: Exports
DEV(boolean indicating development mode) anddeprecated(function to log deprecation warnings). - Usage: Providing feedback to developers about outdated APIs or potential issues without cluttering production logs.
_test-helpers.js
- Purpose: Contains helper functions specifically designed for use within the project's test suite (
*.test.jsfiles). - Usage: Reducing boilerplate and simplifying common testing patterns.
Structure
src/
└── lib/
├── settleAll.js
├── slugify.js
├── slugify.test.js
├── warning.js
└── _test-helpers.js
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 · 40 lines · 324 tokens per session scan A 4ef618644237
Lib is a cursor rule published in the GitHub repository StratoKit/strato-db (14 stars, last pushed 6mo ago), licensed MIT. It adds 324 tokens to every session, about $0.0016 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
cursorrules
CLAUDE.md.
telegram-bot-tests
Test conventions for Telegram Bot library.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
archive-comprehensive
Comprehensive archiving approach for Level 4 Complex System tasks.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
build-test
Process map for VAN QA minimal build test.