cursorrules

Editor rules for working with SQL and Tinybird, a service for building data pipelines and APIs from SQL files.

In plain words
What is it for?
Use them when creating or changing Tinybird data sources and pipes.
Why use it?
They give the agent project-specific guidance for .datasource and .pipe files.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/jhonsfran/unprice/cursorrules
Clone the repo
git clone --depth 1 https://github.com/jhonsfran/unprice

Made for: Cursor.

Per session 5,419 This file is loaded in full into every session.
When invoked 5,419 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.05419 $0.05419
Opus 5 $0.02710 $0.02710
Sonnet 5 $0.01084 $0.01084
Haiku 4.5 $0.00542 $0.00542

Measured 2d ago against content hash 3355a3d09cdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 2d 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.

.cursor/rules/.cursorrules · 289 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 289 lines · 5,419 tokens per session scan A 3355a3d09cdb

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository jhonsfran/unprice (36 stars, last pushed 5d ago), licensed AGPL-3.0. It adds 5,419 tokens to every session, about $0.0271 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-08-30.