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/code-tsnpx skills add gridaco/grida --skill code-tsgit 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.00099 | $0.01185 |
| Opus 5 | $0.00049 | $0.00593 |
| Sonnet 5 | $0.00020 | $0.00237 |
| Haiku 4.5 | $0.00010 | $0.00119 |
Grade A, and why
code-ts 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-ts
Vanilla TS conventions (PascalCase types, kebab-case files, use-*
hooks) are table stakes — assume them. This is the taste on top.
Where naming decides the boundary of a module,
code-ts decides what the code inside that boundary looks like so it
stays testable and the boundary keeps doing its job.
One class or one namespace per file
The exported unit should be a single thing a test can target: one
class with cohesive methods, or one export namespace (or
const-as-namespace) wrapping related functions. Avoid the
alternative — a file that exports ten free functions and a handful
of types side-by-side.
Why:
import { css } from "./css"then asserting againstcss.toReactCSSProperties(...)mirrors the file's structure 1:1. Tests, callers, and grep all read the same shape.- Scattering free
exports loses the gatenamingworked to establish. The file becomes a bag — anything can drift in alongside. - The unit becomes mockable and replaceable as a contract, not a pile of helpers.
The repo lives this. editor/grida-canvas/data-transfer.ts is a
24-line export namespace datatransfer carrying a type, a key, and
an encode/decode pair, and nothing else.
editor/grida-canvas-utils/css.ts is a single export namespace css
with ~20 CSS-conversion functions inside, paired one-to-one with
editor/grida-canvas-utils/css.test.ts. editor/grida-canvas/editor.ts
is the Editor class — the engine's front door, one contract
surface for everything downstream.
Not class or namespace everywhere
This is not "always use a class" or "always use a namespace." It is that the code most worth grouping in this repo — engine logic, library modules, contract-bearing utilities — is overwhelmingly stateful or spec-bearing, and reads better that way. UI glue, route handlers, one-shot scripts, and small page-local helpers can be plain exports.
Heuristic: if the filename is a noun that naming would approve
(one concept, strict, honest), the contents probably want to live
under that noun as a class or namespace. If the file is named for
its location in a feature flow (page.tsx, loader.ts,
route.ts), free exports are fine.
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 · 118 lines · 99 tokens per session scan A 142946005407
code-ts is a skill published in the GitHub repository gridaco/grida (2,624 stars, last pushed 11d ago), licensed Apache-2.0. It adds 99 tokens to every session and 1,185 once invoked, about $0.0005 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…