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/nothing/researchnpx skills add gridaco/nothing --skill researchgit clone --depth 1 https://github.com/gridaco/nothingWhat 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.00058 | $0.02403 |
| Opus 5 | $0.00029 | $0.01202 |
| Sonnet 5 | $0.00012 | $0.00481 |
| Haiku 4.5 | $0.00006 | $0.00240 |
Grade A, and why
research 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Research Skill
Workflow for going from "how does X work?" to a documented survey grounded in prior art from upstream and peer projects.
When to Use This Skill
- Investigating how a browser engine solves a rendering/layout/compositing problem
- Looking up undocumented Skia API behavior
- Understanding CSS feature semantics before adding support
- Comparing canvas editor architectures (excalidraw, tldraw)
- Writing or extending
docs/wg/research/documents
How to Orient Yourself
Before touching any external repo, check what Grida already knows.
| What you need | How to find it |
|---|---|
| Existing research on a topic | docs/wg/research/chromium/index.md (topic map) |
| Code that cites sources | grep "based on|adapted from|ported from" --include="*.rs" |
| Vendored third-party code | ls third_party/ |
| Feature docs for a subsystem | ls docs/wg/feat-*/ |
If already documented, cite it and move on.
Reference Repositories
Local clones (optional): If ~/Documents/GitHub/ exists, it may contain default-style clones (sibling dirs named by repo, e.g. skia). Prefer searching there before cloning or using only the web.
| Repo | Lang | When to reference | Key paths |
|---|---|---|---|
| chromium | C++ | Skia usage, compositing, layer trees, paint scheduling, tiling, GPU resources | cc/ third_party/blink/renderer/ components/viz/ |
| skia | C++ | Undocumented API behavior, GPU internals, filter details | src/gpu/ src/core/ src/effects/ |
| rust-skia | Rust | Rust binding ergonomics — our direct skia-safe dependency |
skia-safe/src/ |
| resvg | Rust | SVG rendering, path conversion, filter effects | crates/resvg/src/ crates/usvg/src/ |
| servo | Rust | CSS layout, DOM, Rust browser-engine patterns. We vendor its style system | components/style/ components/layout/ |
| stylo | Rust | CSS parsing and style resolution | style/ |
| taffy | Rust | Flexbox/Grid layout algorithms | src/tree/ src/compute/ src/style/ |
| excalidraw | TS | Canvas API optimization, rendering heuristics, interaction | packages/excalidraw/renderer/ |
| tldraw | TS | CRDT state model, modular SDK, DOM/SVG canvas | packages/editor/ packages/store/ |
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 · 158 lines · 58 tokens per session scan A bb3fb8b592e8
research is a skill published in the GitHub repository gridaco/nothing (43 stars, last pushed 2d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,403 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
freya
Freya Rust GUI framework best practices, patterns, and conventions. Use when writing Freya components, hooks, elements, or working on a Freya project.
docs-svg-kit
Author SVG figures for Grida docs — diff-able, version-controlled vector diagrams embedded in doc pages instead of screenshots. Provides reusable primitives (selection chrome, size badges, anchor pins, resize cursors, click ripples), color/typography tokens, a starter template, and finished examples to crib from.…
editor-perf
Guides performance investigation, benchmarking, and optimization of the Grida Canvas web editor (TypeScript reducer, Immer, React hooks). Use when profiling reducer dispatch cost, diagnosing slow interactions (drag, resize, color change), writing or running editor benchmarks, instrumenting with PerfObserver, or…
sdk-seam
Discipline for the seam between two SDKs (or two sides of one contract) that the same hand writes. The failure mode: "we own both sides" produces dirty contracts no foreign reviewer would accept. The exercise: pretend the other side is FFI, IPC, or a network protocol you cannot rewrite. Spawn an adversarial subagent…
ai-models
Research, compare, and update AI model configurations. Covers text model tiers, image and video generation models, image tool models, pricing data sourcing, and provider-cost metering against prepaid org credit. Use when bumping model versions, adding new models, updating pricing, or auditing model specs against…
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…