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/ee/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/ee)<a href="https://agentmods.dev/skills/gridaco/grida/ee"><img src="https://agentmods.dev/badge/skills/gridaco/grida/ee/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/ee"><img src="https://agentmods.dev/badge/skills/gridaco/grida/ee.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.00103 | $0.01422 |
| Opus 5.5 | $0.00041 | $0.00569 |
| Sonnet 5.5 | $0.00021 | $0.00284 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
ee 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 17d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ee
Grida is open source. Some features only exist because Grida is also a hosted commercial product — org-level entitlement, custom domains, billing. Those features are EE (enterprise edition): they ship in the same monorepo as the OSS core, but a self-hoster running the codebase without paid infrastructure should be able to identify and strip them.
This skill is the anchor for that boundary. No GRIDA-EE marker
exists in the repo today; this skill establishes the convention.
What counts as EE
The test: would this feature still make sense in a single-user, no-billing self-hosted instance? If no, it is EE.
Three surfaces today:
- Org / entitlement — the commercial layer on top of multi-tenant
routing. Paid plans, member seats, the entitlement check that gates
paid features. The tenant routing substrate itself (
(tenant)route group, RLS, hostname resolution) is OSS infrastructure — only the commercial layer on top of it is EE. - Custom domains (BYOD) — user-owned apex + subdomain mapping on Vercel. See multi-tenant-custom-domain-vercel.
- Billing — subscriptions, AI credit, the entitlement gate
primitive. Platform billing handles the financial engine and policy.
Grida retains its integration consumers; see
platform-consumersfor that workflow.
The GRIDA-EE marker
Like GRIDA-SEC, the boundary is grep-able. Tag every file that
exists only for EE, with the surface as the sub-label:
// GRIDA-EE: entitlement — paid-plan gate
// GRIDA-EE: byod — apex domain verification
// GRIDA-EE: billing — see platform-consumers
Sub-labels are surface names (entitlement / byod / billing),
not ids — there is no central registry like SECURITY.md. The grep
is the index:
grep -rn 'GRIDA-EE' editor crates packages
Tag the file header when the entire file is EE; tag inline when only a branch is EE.
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.
- 17d ago Changed · -1 lines 2d9af7d2a16b
- 18d ago Changed · +3 lines 5788036ef2ff
- 2mo ago First seen · 129 lines · 103 tokens per session scan A d1ac4a8df6e7
ee is a skill published in the GitHub repository gridaco/grida (2,693 stars, last pushed 11d ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,422 once invoked, about $0.0004 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.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
new-entity
Create a backend entity with EF Core configuration and migration.
trading-manual-writer
A writing skill for creating sections of a trading manual for beginners and individual investors. It explains financial instruments or trading topics in Markdown and can include SVG illustrations.
multi-expert-analyzer
A method for examining complicated questions through several expert viewpoints, followed by fact-checking and criticism.
find-postgres-bug
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core dumps), fuzz it (sqlsmith) until the backend crashes, triage the core into a minimal reproducer (MRE), git-bisect the…