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/securitynpx skills add gridaco/grida --skill securitygit 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.00118 | $0.01238 |
| Opus 5 | $0.00059 | $0.00619 |
| Sonnet 5 | $0.00024 | $0.00248 |
| Haiku 4.5 | $0.00012 | $0.00124 |
Grade A, and why
security 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security boundaries — GRIDA-SEC
What GRIDA-SEC-<id> means
Each GRIDA-SEC-<id> is a prevented vulnerability — a class of
attack that would exist by default but the codebase structurally
forecloses. Unlike a CVE (which describes something that was broken),
a GRIDA-SEC id is a contract: this specific class of attack is
impossible because of these specific files, and we keep it that way.
/SECURITY.md is the canonical registry. Every id has a section there
with:
- What it protects — the boundary in plain English.
- Vulnerable scenario — the attack that would exist without the boundary.
- How the code prevents it — the enforcement mechanism, file by file.
- Files bound by this id — the exact files whose contents make up the contract.
Working with tagged code
When you see GRIDA-SEC-<id> in a file you're touching:
- Read the entry in
/SECURITY.mdfor that id. Don't act on the tag alone — the rules are spelled out there. - Run
grep -rn GRIDA-SEC-<id> .to find every other file in the contract. Changes that look local often aren't — a tagged file is load-bearing for the boundary. - Don't remove a tag without removing the entry from
/SECURITY.mdin the same change, with a written justification.
Mandatory security review before commit
If your change touches any file containing a GRIDA-SEC-<id> tag, you
must complete a security review before committing. The review is
brief but explicit:
- Re-read the entry in
/SECURITY.mdfor everyGRIDA-SEC-<id>that appears in your diff. Confirm the prevented scenario is still prevented after your change. - Walk the enforcement mechanism. For each numbered "How the code prevents it" step in the entry, point at the line in your diff (or confirm it's untouched) that satisfies that step.
- Verify all tagged files are still tagged. A rename, refactor, or move that drops the tag is a contract violation, even if behavior looks identical.
- If you added or removed a file from the boundary, update the
"Files bound by this id" list in
/SECURITY.mdin the same commit. - Run any tests adjacent to the boundary. The SECURITY.md entry
for the id may list specific tests; use
grep -rn GRIDA-SEC-<id> --include='*test*' --include='*spec*'to find any others.
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 · 106 lines · 118 tokens per session scan A 6831a6c6c860
security is a skill published in the GitHub repository gridaco/grida (2,624 stars, last pushed 11d ago), licensed Apache-2.0. It adds 118 tokens to every session and 1,238 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…
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…