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 skills/rilldata/agent-skills/rill-rillyamlnpx skills add rilldata/agent-skills --skill rill-rillyamlgit clone --depth 1 https://github.com/rilldata/agent-skillsWrote 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/skills/rilldata/agent-skills/rill-rillyaml)<a href="https://agentmods.dev/skills/rilldata/agent-skills/rill-rillyaml"><img src="https://agentmods.dev/badge/skills/rilldata/agent-skills/rill-rillyaml.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 | $0.00017 | $0.03994 |
| Opus 5 | $0.00009 | $0.01997 |
| Sonnet 5 | $0.00003 | $0.00799 |
| Haiku 4.5 | $0.00002 | $0.00399 |
Grade A, and why
rill-rillyaml 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions for developing rill.yaml
Introduction
rill.yaml is a required configuration file located at the root of every Rill project. It defines project-wide settings, similar to package.json in Node.js or dbt_project.yml in dbt.
Core Concepts
Project metadata
There are no required properties in rill.yaml, but it is common to configure:
display_name: Human-readable name shown in the UIdescription: Brief description of the project's purposecompiler: Deprecated property that is commonly found in old projects
Default OLAP connector
The olap_connector property sets the default OLAP database for the project. Models output to this connector by default, and metrics views query from it unless explicitly overridden.
Common values are duckdb or clickhouse. If not specified, Rill initializes a managed DuckDB database and uses it as the default OLAP connector.
Default AI connector
The ai_connector property selects the connector powering AI features (developer agent, AI charts, chat). Point it to an AI connector defined in the project, such as openai, claude, or gemini. Defaults to Rill's built-in AI service.
Mock users for security testing
The mock_users property defines test users for validating security policies during local development. Each mock user can have:
email(required): The user's email addressname: Display nameadmin: Boolean indicating admin privilegesgroups: List of group memberships- Custom attributes for use in security policy expressions
When mock users are defined and security policies exist, a "View as" dropdown appears in the dashboard preview.
Environment variables
The env property sets default values for non-sensitive variables. These can be referenced in resource files using templating syntax ({{ .env.<variable> }}). Sensitive secrets should go in .env instead.
Resource type defaults
Project-wide defaults can be set for resource types using plural keys:
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.
- 5d ago First seen · 406 lines · 17 tokens per session scan A f7521f8a0a50
rill-rillyaml is a skill published in the GitHub repository rilldata/agent-skills (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 3,994 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…