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/gg/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/gg)<a href="https://agentmods.dev/skills/gridaco/grida/gg"><img src="https://agentmods.dev/badge/skills/gridaco/grida/gg/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/gg"><img src="https://agentmods.dev/badge/skills/gridaco/grida/gg.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.00038 | $0.00391 |
| Opus 5.5 | $0.00015 | $0.00156 |
| Sonnet 5.5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
gg 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.
What it actually says
Grida Gateway consumers
Grida's web, CLI and Desktop retain their authenticated native entry points.
Funded product generation is delegated by the server to Grida Gateway; this
repository owns the consumer adapters and product result persistence.
Standalone customer API-key support is separate from the installed login-based
gg provider; do not replace one credential family with the other.
Read the affected adapter in editor/lib/ai/, Platform consumers,
and GRIDA-SEC-006 in SECURITY.md when touching scoped tokens.
The public standalone contract is gateway.grida.ai/llms.txt.
- Preserve authenticated organization resolution and native result DTOs.
- Product workload credentials are server-only; never expose them to a renderer or substitute a customer's API key.
- Keep the existing
gg:ainative audience and scoped lifetime. Account tokens, scoped native tokens and product workload credentials are distinct. - Preserve original accepted job identity during polling, retries and asset persistence. Download failure must not resubmit paid work.
- Do not add financial policy, another credit balance or duplicate native usage to migrated generation. Retained native consumers still use Platform admission.
GRIDA-GG: <surface>marks consumer/token/provider/Desktop code. It does not indicate ownership of the Gateway service or financial engine.
Use focused no-dotenv unit/API tests and editor TypeScript. The paired SDK lane requires an explicitly supplied local service fixture and synthetic credentials; ordinary tests must not load hosted keys or call paid models.
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 · -96 lines · -127 tokens per session 6ef179befc99
- 2mo ago First seen · 132 lines · 165 tokens per session scan A 2693eda18d13
gg is a skill published in the GitHub repository gridaco/grida (2,693 stars, last pushed 11d ago), licensed Apache-2.0. It adds 38 tokens to every session and 391 once invoked, about $0.0002 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.
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.
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…
django-migrations
Django migration patterns and safety workflow for PostHog. Use when creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDatabaseAndState. Also…
new-entity
Create a backend entity with EF Core configuration and migration.
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…