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/slidesnpx skills add gridaco/grida --skill slidesgit 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.00046 | $0.01413 |
| Opus 5 | $0.00023 | $0.00707 |
| Sonnet 5 | $0.00009 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
slides 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A Grida slides deck is a .canvas bundle in slides mode whose documents are
SVG files — one SVG per slide. Today this is Grida's only slide format:
dotcanvas + SVG, and it is the default. When the task is a deck,
presentation, pitch, or talk, build it this way. Do NOT author slides as
markdown or HTML — the slides surface renders SVG only, so anything else won't
appear.
Structure
- The bundle is a folder ending in
.canvaswith a.canvas.jsonmanifest. - Manifest:
editor: "slides",files: ["*.svg"], and adocumentsarray whose ORDER is the running order of the deck.{ "editor": "slides", "files": ["*.svg"], "documents": [ { "src": "001.svg", "id": "cover" }, { "src": "002.svg", "id": "problem" } ] } - Each slide's CONTENT is one SVG file referenced by
src. The deck convention is flat, zero-padded, root-level files:001.svg,002.svg, …. - A slide's human name is its SVG
<title>element — not a manifest field. - If you open an existing or freshly-seeded bundle whose manifest says
editor: "board"but the task is a deck, seteditor: "slides"yourself — the manifest is yours to reconcile with the user's intent.
Slide SVG
Every slide is a full-bleed 16:9 SVG on the SAME 1920×1080 viewBox, so the
deck stays uniform. Start each from this shape:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1920 1080" width="1920" height="1080">
<title>Cover</title>
<rect width="1920" height="1080" fill="#0b1220"/>
<text x="160" y="560" font-family="Inter, Arial, sans-serif" font-size="120" font-weight="700" fill="#ffffff">Your title</text>
</svg>
Working pattern
- To start a deck: first make the bundle folder — a NEW directory whose name
ends in
.canvas(e.g.Q3 Report.canvas/), created under your working root. The.canvassuffix on the FOLDER is what marks it a bundle (see Structure); a plain folder — or files loose in the workspace root — is NOT a deck and won't open. Thenwrite_fileeach slide as<name>.canvas/NNN.svgandwrite_filethe manifest as<name>.canvas/.canvas.jsonlisting them in order. Every file lives INSIDE that one.canvasfolder. - To edit a deck:
read_file.canvas.jsonfirst (preserveversion/$schemaand any unknown fields), edit the slide SVGs, then write the full manifest back withdocumentsin the intended order. - Reorder = reorder
documents. Add a slide =write_filea newNNN.svgand insert it intodocuments. Remove = drop it fromdocuments.
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 · 113 lines · 46 tokens per session scan A 299f2c1d2a62
slides is a skill published in the GitHub repository gridaco/grida (2,629 stars, last pushed 12d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,413 once invoked, about $0.0002 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-ui-patterns
Design system UI patterns for Supabase Studio. Use when building or updating pages, forms, tables, charts, empty states, navigation, cards, alerts, or side panels (sheets). Covers layout selection, component choice, and placement conventions.
io-svg
Guides work on SVG import into the Grida Canvas Rust engine (grida crate). Covers crates/grida/src/import/svg/, the gridadev svg-to-grida CLI, cross-boundary FBS codec tests (Rust encode → TS decode), SVG fixture authoring, and known SVG import limitations (text model, filters, transforms). Use when adding SVG feature…
refine-canvas-strokes
Design, implement, review, or troubleshoot safe refinement of editable 2D canvas strokes. Use for handwriting smoothing, automatic text layout cleanup, optional font-guided handwriting normalization, freehand cleanup, geometric shape snapping, diagram cleanup, stroke-style normalization, semantic stroke replacement…
canvas-design
Use when design visual art and graphics using HTML5 Canvas, p5.js, or SVG. Create generative art, data visualizations, diagrams, and interactive graphics. Use when designing visual art and graphics using html5 canvas, p5.js, or.
canvas-design
Design philosophy docs and canvas-based visual creation. Use when articulating design principles, crafting multi-page design documents, or exploring aesthetic philosophy with intentional design thinking.
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…