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/seonpx skills add gridaco/grida --skill seogit 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.00126 | $0.02028 |
| Opus 5 | $0.00063 | $0.01014 |
| Sonnet 5 | $0.00025 | $0.00406 |
| Haiku 4.5 | $0.00013 | $0.00203 |
Grade A, and why
seo 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 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.
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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO
Guidelines for search engine optimization across the Grida project -- Next.js pages, blog posts, and documentation.
Scope
| Surface | Location | Framework |
|---|---|---|
| Marketing / product pages | editor/app/(www)/ |
Next.js 16 |
| Blog | docs/blog/ or apps/docs/blog/ |
Docusaurus |
| Documentation | docs/** |
Docusaurus |
| Sitemaps | editor/app/sitemap.ts + others |
Next.js |
Next.js Pages (editor/app/(www))
Metadata
Every public page must export metadata (static or dynamic).
// Static
export const metadata: Metadata = {
title: "Page Title — Grida",
description: "Concise, keyword-rich description under 160 chars.",
keywords: ["relevant", "keywords"],
openGraph: {
title: "Page Title — Grida",
description: "Same or tailored OG description.",
images: ["/og/page-name.png"],
},
twitter: {
card: "summary_large_image",
},
};
// Dynamic
export async function generateMetadata({ params }): Promise<Metadata> { ... }
Rules:
titleshould end with— Grida(or use atitle.templatein the root layout).descriptionmust be unique per page, under 160 characters, and include primary keywords.- Every page with OG images must set
metadataBaseor use absolute URLs so crawlers resolve them correctly. - OG images must return 200 without auth and use correct
Content-Type.
metadataBase
When openGraph.images uses relative paths, the layout or page must set:
metadataBase: new URL("https://grida.co"),
Without this, crawlers may see broken OG URLs.
Sitemap
Public pages belong in editor/app/sitemap.ts.
{
url: "https://grida.co/new-page",
changeFrequency: "monthly",
priority: 0.5,
}
- Use
priority: 1only for the homepage. - Match
changeFrequencyto actual update cadence. - When adding a new public page, always add a sitemap entry.
- Sitemaps are split per route group (root,
/packages,/library, …). A newsitemap.tsis invisible to crawlers until it's added as aSitemap:line ineditor/app/robots.txt— non-root sitemaps are not auto-discovered. - Prefer deriving sitemap entries from the page's data source (see
packages/sitemap.ts) over hand-maintained URL lists, which drift.
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 · 243 lines · 126 tokens per session scan A 1ad8591fcdfd
seo is a skill published in the GitHub repository gridaco/grida (2,629 stars, last pushed 11d ago), licensed Apache-2.0. It adds 126 tokens to every session and 2,028 once invoked, about $0.0006 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
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…
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…
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…