Rill is a business intelligence tool for turning data sources into SQL models, metrics, dashboards, and natural-language analysis. It is used by business users and coding agents, with OLAP engines such as ClickHouse and DuckDB supporting its queries. Its catalogue add-ons support agent-driven work on Rill projects.
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.
git clone --depth 1 https://github.com/rilldata/rillWrote 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/rilldata/rill/naming-conventions)<a href="https://agentmods.dev/rules/rilldata/rill/naming-conventions"><img src="https://agentmods.dev/badge/rules/rilldata/rill/naming-conventions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/rilldata/rill/naming-conventions"><img src="https://agentmods.dev/badge/rules/rilldata/rill/naming-conventions.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00503 |
| Opus 5.5 | $0.00000 | $0.00201 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
naming-conventions 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 1mo 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.
What it actually says
Naming Conventions
File Naming Rules
TypeScript/JavaScript Files
- Use kebab-case for all TypeScript and JavaScript files
- Examples:
user-management.ts,environment-variables.ts,project-status.ts
Svelte Component Files
- Use PascalCase for Svelte component files
- Examples:
ProjectCard.svelte,UserManagement.svelte,EnvironmentVariables.svelte - Exception: Use kebab-case for layout files (e.g.,
+layout.svelte,+page.svelte)
Directory Naming
- Use kebab-case for all directories
- Examples:
user-management/,environment-variables/,project-status/
Component Naming Rules
Svelte Components
- Use PascalCase for component names in Svelte files
- Examples:
<ProjectCard />,<UserManagement />,<EnvironmentVariables /> - Match the component name to the file name
TypeScript Interfaces/Types
- Use PascalCase for interfaces and types
- Examples:
ProjectPermissions,UserManagement,EnvironmentVariable
Variable and Function Naming
Variables
- Use camelCase for variables and constants
- Examples:
projectPermissions,environmentVariables,userManagement
Functions
- Use camelCase for function names
- Use descriptive verbs:
getProjectPermissions(),updateEnvironmentVariables(),validateUserInput()
Constants
- Use UPPER_SNAKE_CASE for true constants
- Examples:
MAX_FILE_SIZE,DEFAULT_TIMEOUT,API_BASE_URL
Special Cases
Test Files
- Use the same naming as the source file with
.specsuffix
Configuration Files
- Use kebab-case for configuration files
- Examples:
tailwind.config.ts,vite.config.ts,svelte.config.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.
- 1mo ago First seen · 78 lines · 0 tokens per session scan A ea2869dc5973
naming-conventions is a cursor rule published in the GitHub repository rilldata/rill (2,967 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 503 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-08-30.
Other cursor rules, from other repositories
svelte
You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.
testing
Shared Svelte testing guidance.
global
ALWAYS follow this rule.
code-organization
Code and file organization standards.
dependencies
Dependency management guidelines.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.