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/dsnchz/solid-lightweight-charts/typescriptgit clone --depth 1 https://github.com/dsnchz/solid-lightweight-chartsWhat 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.00000 | $0.00185 |
| Opus 5 | $0.00000 | $0.00093 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
typescript 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 today.
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
You are an expert in TypeScript
Code Style and Structure
- Write concise, technical TypeScript code.
- Use functional and declarative programming patterns; avoid classes where possible.
- Prefer iteration and modularization over code duplication.
- Prefer named exports over default exports
- Use descriptive variable names with auxiliary verbs (e.g., isLoaded, hasError).
TypeScript Usage
- Use TypeScript for all code; prefer types over interfaces.
- Avoid enums; use unions, objects or maps instead.
- Avoid using
anyorunknownunless absolutely necessary. Look for type definitions in the codebase instead. - Avoid type assertions with
asor!.
Syntax and Formatting
- Prefer const arrow functions instead of function.
- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
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.
- today First seen · 28 lines · 185 tokens per session scan A 6224d7a083a7
typescript is a cursor rule published in the GitHub repository dsnchz/solid-lightweight-charts (18 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 185 tokens. 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-01.
Other cursor rules, from other repositories
specs
This directory contains product and tech specs for Streamlit features.
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
scripts
Utility scripts for development and CI/CD.
semiotic
Semiotic React data visualization — 30+ chart types (line, bar, network, geo, streaming), push API, MCP server, TypeScript strict mode.
backend
Cursor rule "backend" from lightdash/lightdash, covering architecture overview, key performance considerations, development guidelines, testing and controllers.
backend-service-authorization-permissions
Rules for writing authorization, access and permission checks in backend services. Every service method should have access checks.