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/omtodkar/librarian/cursorgit clone --depth 1 https://github.com/omtodkar/librarianWhat 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 | $0.00227 | $0.00227 |
| Opus 5 | $0.00113 | $0.00113 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
cursor 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.
This is a copy
100% identical to librarian — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Librarian
This project uses Librarian for semantic search and graph-based code navigation.
State lives in .librarian/.
When to use Librarian
Before grep, find, or opening files at random, try:
librarian search "<topic>"— semantic search over docs + codelibrarian context "<topic>"— deep briefing: related docs + code refslibrarian neighbors <node>— what does X connect to?librarian path <from> <to>— how do these pieces relate?
For architecture or "how does X work" questions, librarian context returns a
curated briefing — faster and denser than reading files one by one.
Graph report
.librarian/out/GRAPH_REPORT.md is a topology snapshot. Read it first when
orienting in an unfamiliar area of the codebase.
See .librarian/rules.md for the authoritative guidance.
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 · 29 lines · 227 tokens per session scan A b6446b7a7a3a
cursor is a cursor rule published in the GitHub repository omtodkar/librarian (2 stars, last pushed 3mo ago), licensed MIT. It adds 227 tokens to every session, about $0.0011 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to librarian, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.