agentmods.dev

deploy-schema

deploy-schema is a command for Claude Code from sanity-io/agent-toolkit. It costs 14 tokens per session (337 once invoked), scanned A, original, MIT.

A command workflow for publishing a Sanity content schema—the definition of the document types and fields used by a Sanity project—to Sanity's online Content Lake.

In plain words
What is it for?
Use it after adding or changing document types, fields, or validation rules, especially before using Sanity content tools that depend on the updated schema.
Why use it?
It checks the schema before publishing, warns about possible breaking changes, and verifies that the new types and fields are available afterward.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sanity plugin — 9 skills, 4 commands, 1 MCP server shipped together

not rated 191repo +3 4d ago A scan 14 tokens original MIT

Good fit Use it after adding or changing document types, fields, or validation rules, especially before using Sanity content tools that depend on the updated schema.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/sanity-io/agent-toolkit/deploy-schema
View source ↗ sanity-io/agent-toolkit sanity.io
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/sanity-io/agent-toolkit

Made for: Claude Code.

Or install sanity, the plugin that ships this one along with the rest of its 9 skills, 4 commands, 1 MCP server.

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 deploy-schema

README.md
[![agentmods](https://agentmods.dev/badge/commands/sanity-io/agent-toolkit/deploy-schema/github.svg)](https://agentmods.dev/commands/sanity-io/agent-toolkit/deploy-schema)
Your own site
<a href="https://agentmods.dev/commands/sanity-io/agent-toolkit/deploy-schema"><img src="https://agentmods.dev/badge/commands/sanity-io/agent-toolkit/deploy-schema/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 deploy-schema

Your own site · 80×15
<a href="https://agentmods.dev/commands/sanity-io/agent-toolkit/deploy-schema"><img src="https://agentmods.dev/badge/commands/sanity-io/agent-toolkit/deploy-schema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00014 $0.00337
Opus 5.5 $0.00006 $0.00135
Sonnet 5.5 $0.00003 $0.00067
Haiku 4.5 $0.00001 $0.00034

Measured 1mo ago against content hash 242db995c077, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deploy-schema 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 1mo 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.

commands/deploy-schema.md · 60 lines

What it actually says

Deploy Sanity Schema

I'll help you deploy your schema to the Sanity Content Lake.

Why Deploy Schema?

Schema deployment is required for:

  • ⚠️ MCP Server content operations (create_documents, patch_documents) to use the latest schema
  • Embedded Studios
  • Scheduled Publishing
  • Cloud Functions with schema validation

Deployment Command

npx sanity schemas deploy

What I'll Do

  1. Pre-Deploy Check

    • Verify schema syntax (run typegen)
    • Check for breaking changes
    • Warn about removed fields with data

  2. Deploy

    • Run npx sanity schemas deploy
    • Confirm success

  3. Post-Deploy Verification

    • Use MCP get_schema to verify deployment
    • Confirm new types/fields are available

When to Deploy

Scenario Deploy?
Added new document type ✅ Yes
Added/modified fields ✅ Yes
Changed validation rules ✅ Yes
Using MCP content tools after schema changes ✅ Yes
Local dev only (no MCP) Optional

Important Notes

  • Schema deployment is fast (~2 seconds)
  • Does NOT deploy the Studio app (use npx sanity deploy for that)
  • Always deploy before MCP content operations after schema changes

Usage

"Deploy my schema" "Check if my schema is deployed" "Why can't MCP see my new field?"

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. 1mo ago First seen · 60 lines · 14 tokens per session scan A 242db995c077

Subscribe to this mod's changes

deploy-schema is a command published in the GitHub repository sanity-io/agent-toolkit (191 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 337 once invoked, about $0.0001 per session on Opus 5.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.

Claude CodeCloudDevOps and cloudai-rulesclaude-code-plugincursor-aimcpmcp-server
Related

Other commands, from other repositories

setup-video-vision

Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.

jordanrendric/claude-video-vision · 20 tokens

cloudflare-workers:optimize

Analyze and optimize Cloudflare Workers performance. Checks bundle size, caching, memory usage, and provides actionable recommendations.

secondsky/claude-skills · 29 tokens

cloudflare-workflows:create

Quick scaffold for new workflow class in existing project. Use when user wants to add another workflow to existing project without full setup wizard.

secondsky/claude-skills · 32 tokens

create-epo-patent

Create a complete EPO-compliant patent application from invention disclosure through filing-ready package.

RobThePCGuy/Claude-Patent-Creator · 16 tokens

cccs-guidance

CCCS assessment process and certified cloud provider guidance.

GRCEngClub/claude-grc-engineering · 9 tokens

nyann:apply

Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…

thettwe/nyann · 85 tokens