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/security/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/security)<a href="https://agentmods.dev/skills/gridaco/grida/security"><img src="https://agentmods.dev/badge/skills/gridaco/grida/security/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/security"><img src="https://agentmods.dev/badge/skills/gridaco/grida/security.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.00118 | $0.01296 |
| Opus 5.5 | $0.00047 | $0.00518 |
| Sonnet 5.5 | $0.00024 | $0.00259 |
| Haiku 4.5 | $0.00012 | $0.00130 |
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 1mo 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 — 111 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.
- 1mo ago Changed · +5 lines b51d83e12cf9
- 2mo ago First seen · 106 lines · 118 tokens per session scan A 6831a6c6c860
security is a skill published in the GitHub repository gridaco/grida (2,693 stars, last pushed 11d ago), licensed Apache-2.0. It adds 118 tokens to every session and 1,296 once invoked, about $0.0005 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.
database
Relational database authority — PostgreSQL, async ORM (SQLAlchemy 2 / asyncpg), Alembic schema migrations, Supabase Python and JS clients, query optimisation, index strategy, connection pooling, transaction patterns, and bulk operations across Python and Node stacks.
whodb
Work with WhoDB platform hosts and project resources via MCP, including multiple environments, or query databases directly in database-only MCP mode.
schema-designer
Help design database schemas, create tables, and plan data models. Activates when users ask to create tables, design schemas, or model data relationships.
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
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.