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/fixturesnpx skills add gridaco/grida --skill fixturesgit 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.00053 | $0.00757 |
| Opus 5 | $0.00026 | $0.00378 |
| Sonnet 5 | $0.00011 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
fixtures 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixtures
What fixtures are
Fixtures are static input files — .fig archives, clipboard captures,
markdown samples, .grida documents — used as deterministic inputs to
parsing and I/O tests. They exist so that tests are reproducible,
self-contained, and don't depend on external services or generated data.
Why we keep them
- Regression detection — parse the same input, compare the output.
- Spec coverage — each fixture maps to a specific feature or edge case being tested (one concept per file).
- Onboarding — new contributors can see exactly what the importers handle by browsing fixtures.
Best practices
- One concept per file. Don't combine unrelated properties.
- Self-contained. No external resources, network fetches, or scripts.
- Minimal. Only enough structure to isolate the behavior under test.
- Descriptive naming.
<domain>-<property>[-<descriptor>].<ext>— the filename alone should tell you what's being tested. - Don't duplicate. Before adding a fixture, check if an existing one already covers the behavior. Extend or split rather than duplicate.
The tree — who owns what
fixtures/
├── test-fig/ # Figma clipboard / .fig fixtures (LFS: *.fig, *.deck)
├── test-figma/ # Figma archive / REST fixtures
├── test-canvas/ # .canvas (dotcanvas) fixtures
├── test-markdown/ # Markdown fixtures
├── fonts/ # ← FROZEN SNAPSHOT (engine-owned)
├── images/ # ← FROZEN SNAPSHOT (engine-owned)
├── test-grida/ # ← FROZEN SNAPSHOT (engine-owned)
└── text-editor/ # ← FROZEN SNAPSHOT (engine-owned)
Frozen snapshots
The engine repo owns the canonical, evolving copies of fonts/, images/,
test-grida/ and text-editor/ (its crates consume them at compile/test
time, with full git history carried over). The copies here exist only so
staying tests keep passing at their original paths — consumers:
@grida/fonts, @grida/refig, @grida/io, the editor reducer round-trip,
@grida/text-editor. Do not edit them here; re-snapshot deliberately
from the engine repo if the canon evolves. See
fixtures/README.md.
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 · 70 lines · 53 tokens per session scan A 9e734d0bf1dc
fixtures is a skill published in the GitHub repository gridaco/grida (2,629 stars, last pushed 11d ago), licensed Apache-2.0. It adds 53 tokens to every session and 757 once invoked, about $0.0003 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
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…
studio-testing
Testing strategy for Supabase Studio. Use when writing tests, deciding whether a change needs tests and which type, extracting logic from components into testable utility functions, or reviewing test coverage. Covers unit tests, component tests, and E2E test selection criteria.
vitest
Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering. Use for Vitest API and configuration questions anywhere in the monorepo; for Studio-specific test strategy and component-test setup, start with studio-testing and…
fixtures
Guides authoring, organizing, and referencing test fixtures across the engine repo. Use when creating new fixtures, writing tests that depend on fixtures, or deciding what should be checked into git.
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…