Grida is an open-source graphics workspace that combines an infinite canvas editor, SVG tools, a database and CMS, and forms. Designers and developers use it to create, import, render, and manage visual documents and connected data, while the catalogue add-ons support its workflows.
Borrowing it
Nothing to install: this file belongs to gridaco/grida. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gridaco/grida/main/.agents/skills/grounding/SKILL.mdgit clone --depth 1 https://github.com/gridaco/gridaWrote 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/gridaco/grida/grounding)<a href="https://agentmods.dev/skills/gridaco/grida/grounding"><img src="https://agentmods.dev/badge/skills/gridaco/grida/grounding/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/skills/gridaco/grida/grounding"><img src="https://agentmods.dev/badge/skills/gridaco/grida/grounding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00123 | $0.01115 |
| Opus 5.5 | $0.00049 | $0.00446 |
| Sonnet 5.5 | $0.00025 | $0.00223 |
| Haiku 4.5 | $0.00012 | $0.00112 |
Grade A, and why
grounding 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 27d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grounding
Grounding is establishing what is actually true and current for the surface you are about to change, then acting on that — not on a guess, a memory, or the first grep hit. The hard part is not search; it is picking the authoritative source and reconciling sources that disagree.
Intentional seed. This holds only Grida-specific facts that are not obvious from
CLAUDE.md/AGENTS.md. Grow it from real, discovered specifics (concept→file anchors that bite repeatedly, conflicts that actually happened and how they resolved). Do not pad it with generic search advice a competent agent already knows.
Source of truth (scoped to the surface)
Authority is per-surface — the engine model and its TS mirror can each be right for their own surface and still disagree. Name the surface, then trust:
- Canvas render/node model → the Rust engine, now in the engine repo:
https://github.com/gridaco/nothing/blob/main/crates/grida/src/node/schema.rs.
The TS mirror
editor/grida-canvas/is authoritative for editor behavior and can lag the engine. - DB schema →
supabase/migrations/(applied, immutable);supabase/schemas/*.sqlis a readable projection that can lag — use the database skill. - Shared AI catalogue and input contracts → repository-root
data/ai/facts.json,data/ai/service.json, anddata/ai/inputs.json. Edit these authored sources; marked TypeScript literals andcrates/grida-ai/data/assets are generated consumers. Followai-modelsfor authoring and regeneration. - Directory contract → the nearest
AGENTS.md/README.md. - "I remember API X…" → re-read current code; a memory is a claim about a past state, verify before acting.
Disagreement → decide which wins and why (git log -1 recency, what
the running entrypoint imports, what tests assert); don't average;
surface a material conflict to the user. Never authoritative even when
they match: docs/_history/,
docs/@designto-code/ (synced — truth is upstream), .ref/.
docs/cli/ is the replacement CLI's maintained user guide; only its explicitly
retired legacy pages are historical. Follow docs/AGENTS.md for that boundary.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 27d ago Changed · +5 lines 5c17f8fb43b3
- 1mo ago Changed · +1 lines 7eaf5ee7e940
- 2mo ago First seen · 90 lines · 123 tokens per session scan A 871f0780544c
grounding is a skill published in the GitHub repository gridaco/grida (2,693 stars, last pushed 11d ago), licensed Apache-2.0. It adds 123 tokens to every session and 1,115 once invoked, about $0.0005 per session on Opus 5.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
explorer
Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.
database
Relational database authority — PostgreSQL, async ORM (SQLAlchemy 2 / asyncpg), Alembic schema migrations, Supabase Python and JS clients, query optimisation, index strategy, connection pooling, transaction patterns, and bulk operations across Python and Node stacks.
whodb
Work with WhoDB platform hosts and project resources via MCP, including multiple environments, or query databases directly in database-only MCP mode.
schema-designer
Help design database schemas, create tables, and plan data models. Activates when users ask to create tables, design schemas, or model data relationships.
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
graphjin-env
Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.