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 instructions/gridaco/grida/agents-mdgit 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.02501 | $0.02501 |
| Opus 5 | $0.01251 | $0.01251 |
| Sonnet 5 | $0.00500 | $0.00500 |
| Haiku 4.5 | $0.00250 | $0.00250 |
Grade A, and why
grida AGENTS.md 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 yesterday.
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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hi robots, welcome to the Grida project.
Grida is a open source Design tool that aims to provide high-performance, configurable canvas-based editor.
Mission
- Build a high performance interactive graphics engine and its ecosystem
Currently, we have below features / modules.
- canvas
- forms
- database
Project Structure
When entering an unfamiliar directory, always check for
README.mdandAGENTS.mdfirst. These files contain domain-specific context, conventions, and constraints that override general assumptions. The table below lists the known ones, but sub-directories and individual packages may have their own as well.
| directory | README | AGENTS | notes |
|---|---|---|---|
| docs | - | docs/AGENTS.md |
the docs directory |
| editor | - | editor/AGENTS.md |
the editor directory |
| packages | - | - | shared packages |
| desktop | desktop/README.md |
- | the electron desktop app |
| supabase | supabase/README.md |
supabase/AGENTS.md |
the supabase project |
| apps | - | - | micro sites for Grida |
| jobs | jobs/README.md |
- | hosted jobs |
| test | test/README.md |
test/AGENTS.md |
manual test cases & UX behavior specs |
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.
- yesterday First seen · 247 lines · 2,501 tokens per session scan A c47e08b70326
grida AGENTS.md is an instructions file published in the GitHub repository gridaco/grida (2,624 stars, last pushed 11d ago), licensed Apache-2.0. It adds 2,501 tokens to every session, about $0.0125 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 instructions, from other repositories
supabase studio-telemetry.instructions.md
Instructions for supabase/supabase, covering studio telemetry review rules, when to flag missing telemetry, feature flag telemetry pattern, event naming and event properties.
supabase studio-composition-patterns.instructions.md
Instructions for supabase/supabase, covering react composition patterns review rules, core principle, when to flag, 1. boolean prop proliferation (high) and 2. render props instead of children (medium).
supabase studio-shortcuts.instructions.md
Instructions for supabase/supabase, covering studio shortcut review rules, core principle, when to flag, preferred pattern and search inputs.
supabase studio-e2e-tests.instructions.md
Instructions for supabase/supabase, covering studio e2e test review rules, selector priority (best to worst), patterns to flag and good practices to encourage.
supabase studio-error-handling.instructions.md
Instructions for supabase/supabase, covering studio error handling review rules, architecture, when to flag, correct usage and key files.
supabase copilot-instructions.md
Instructions for supabase/supabase, covering copilot code review instructions, review policy — read this first, confidence threshold, what not to comment on and what to comment on (priority order).