netlify-blobs

netlify-blobs is a cursor rule for Cursor from netlify/context-and-tools. It costs 137 tokens per session (2,959 once invoked), scanned C, original, MIT.

Instructions for storing and retrieving files, uploads, and other unstructured data with Netlify Blobs, a key-value storage service. The data can be used from Netlify Functions, Edge Functions, and build plugins.

In plain words
What is it for?
Use it for user uploads, images, cached data, generated files, form submissions, and other data that does not need a relational database.
Why use it?
It explains how to choose storage shared across deployments versus storage isolated to one deployment, helping prevent test data from affecting production.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: $skill-name invocation.

Good fit Use it for user uploads, images, cached data, generated files, form submissions, and other data that does not need a relational database.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/netlify/context-and-tools/netlify-blobs
Install

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.

Clone the repo
git clone --depth 1 https://github.com/netlify/context-and-tools

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for netlify-blobs

README.md
[![agentmods](https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-blobs/github.svg)](https://agentmods.dev/rules/netlify/context-and-tools/netlify-blobs)
Your own site
<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-blobs"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-blobs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for netlify-blobs

Your own site · 80×15
<a href="https://agentmods.dev/rules/netlify/context-and-tools/netlify-blobs"><img src="https://agentmods.dev/badge/rules/netlify/context-and-tools/netlify-blobs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 137 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,959 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00137 $0.02959
Opus 5.5 $0.00055 $0.01184
Sonnet 5.5 $0.00027 $0.00592
Haiku 4.5 $0.00014 $0.00296

Measured 19d ago against content hash f7cf82f3f23c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

netlify-blobs scanned grade C with 1 finding 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 19d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- system: agent-context/blobs/system.md — human-owned, merged by ctx-gen; edit system.md, not this section -->
cursor/rules/netlify-blobs.mdc · 256 lines

How it starts

The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Netlify Blobs

Modern syntax — import from @netlify/blobs and open a store, then call methods on the handle:

import { getStore, getDeployStore, listStores } from "@netlify/blobs";
import type { Context } from "@netlify/functions"; // or "@netlify/edge-functions"

In Functions, Edge Functions, and Build Plugins, siteID, deployID, token (and region for getDeployStore) are injected automatically. Install with npm install @netlify/blobs.

Not a database. For dynamic, per-user, transactional, or relational data, use Netlify DB. Blobs is for objects, files, and cache-like state, optimized for frequent reads and infrequent writes.

Store scope is a footgun — read this first. getStore opens a site-wide store shared across ALL deploy contexts: code on a deploy preview reads, overwrites, and deletes production data. Never run destructive tests or seed throwaway data from a preview against a site-wide store. Use getDeployStore() or a context-specific store name for isolation.

Choosing a store type

  • getStore(name) — site-wide, shared across all deploys. Data persists across deploys; previews see production data.
  • getDeployStore(name) — deploy-specific, scoped to one deploy. Kept in sync on rollback, cleaned up on deploy deletion. Use for isolation and for anything a failed deploy must not corrupt.
  • Build plugins can READ from any of the site's stores, but WRITE only to deploy-specific stores (getDeployStore). File-based uploads also write only to deploy-specific stores.

Core writes and reads

const uploads = getStore("file-uploads");

// set: value is ArrayBuffer | Blob | string
await uploads.set(key, file, { metadata: { country: "Spain" } });

// setJSON: any JSON-serializable value
await uploads.setJSON(key, { hello: "world" });

// get: returns value or null. type: text (default) | json | arrayBuffer | blob | stream
const entry = await uploads.get(key);            // string
const obj = await uploads.get(key, { type: "json" });
if (entry === null) { /* 404 */ }

Read the full file on GitHub · 256 lines

Changes

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.

  1. 19d ago Changed · +29 lines · -7 tokens per session f7cf82f3f23c
  2. 29d ago Changed · -38 lines · +19 tokens per session 89e177e27de7
  3. 1mo ago First seen · 265 lines · 125 tokens per session scan C 4a3c78e87c80

Subscribe to this mod's changes

netlify-blobs is a cursor rule published in the GitHub repository netlify/context-and-tools (41 stars, last pushed 2d ago), licensed MIT. It adds 137 tokens to every session and 2,959 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.