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/gridaco/grida/desktopnpx skills add gridaco/grida --skill desktopgit clone --depth 1 https://github.com/gridaco/gridaWhat 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.00133 | $0.02988 |
| Opus 5 | $0.00067 | $0.01494 |
| Sonnet 5 | $0.00027 | $0.00598 |
| Haiku 4.5 | $0.00013 | $0.00299 |
Grade A, and why
desktop scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:9222/json/version How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grida Desktop - Electron Shell
This skill is for the Electron shell only: main process, windows, menus,
preload, native protocol/file entry points, and the renderer bridge surface.
The renderer is still the editor's Next.js app under editor/app/desktop/;
Electron URL-loads it from http://localhost:3000/desktop/* in dev and
https://grida.co/desktop/* in prod.
Use agent-system for the daemon + agent-tenant core,
sessions, workspaces, providers, tool execution, HTTP routes, and tests in
packages/grida-daemon and packages/grida-ai-agent.
Adjacent:
securityfor the GRIDA-SEC-004 trust boundary,code-reactfor React code undereditor/app/desktop/**andeditor/scaffolds/desktop/**.
When to use this skill
- Editing
desktop/src/**,desktop/forge.config.ts,desktop/Info.plist, or desktop packaging/dev-server wiring. - Changing
desktop/src/main.ts,window.ts,menu.ts, preload, bridge contract, app branding, host-app integration, deep links, file associations, single-instance behavior, or multi-window routing. - Touching
editor/app/desktop/**,editor/scaffolds/desktop/**, oreditor/lib/desktop/**because the UI depends onwindow.grida. - Debugging "works in browser but not in desktop" or "only repros in Electron" issues.
- Verifying the desktop app through CDP / Playwright.
- Touching CSP or proxy behavior for
/desktop/*. - Auditing whether linked-package or hosted Desktop renderer changes require a native version bump or coordinated release.
Use agent-system to implement core agent behavior that can be tested without
Electron: packages/grida-daemon/**, packages/grida-ai-agent/**, daemon HTTP
routes, sessions, files/workspaces, providers, tools, runtime, skills, and
BYOK/secrets. Also use this skill when auditing whether that work changes the
packaged Desktop payload or its compatibility with the hosted renderer.
Shape
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.
- 2d ago First seen · 328 lines · 133 tokens per session scan A 369939eb4924
desktop is a skill published in the GitHub repository gridaco/grida (2,629 stars, last pushed 11d ago), licensed Apache-2.0. It adds 133 tokens to every session and 2,988 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
react-hook-form
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions, reset, dirty state, number inputs, and controlled-input rules. Load this BEFORE writing or modifying ANY form code, adding a field to an existing form, touching watch/useWatch/formState/getValues/setValue/reset, wiring a form into a…
safe-sql-execution
Use whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint…
studio-e2e-tests
Write and run Playwright E2E tests for Supabase Studio (e2e/studio). Use when asked to run e2e tests, write new E2E tests, or debug flaky or failing Playwright tests. Covers running commands, avoiding race conditions, waiting strategies, selectors, helper functions, and CI vs local differences.
studio-mock-api-tests
Component tests for Supabase Studio that mock API requests at the network layer with MSW. Use when writing or reviewing a component test that exercises a React Query hook or mutation, or when migrating an existing test away from vi.mock('@/data/...'). Covers the customRender + addAPIMock template and the jsdom/MSW…
ask-the-docs
Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding minimalism) when proposing or critiquing changes. Use when the user asks "how does X work in the docs app?", "where does Y…
clickhouse-logs-queries
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint). Use this whenever a task involves Logs Explorer SQL, the logattributes map, querying a log source (edgelogs, postgreslogs, authlogs, etc.), translating an old BigQuery cross join…