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 commands/sanity-io/agent-toolkit/deploy-schemagit clone --depth 1 https://github.com/sanity-io/agent-toolkitWhat 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.00014 | $0.00337 |
| Opus 5 | $0.00007 | $0.00169 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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 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.
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
-
Pre-Deploy Check
- Verify schema syntax (run typegen)
- Check for breaking changes
- Warn about removed fields with data
-
Deploy
- Run
npx sanity schemas deploy - Confirm success
- Run
-
Post-Deploy Verification
- Use MCP
get_schemato verify deployment - Confirm new types/fields are available
- Use MCP
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 deployfor 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?"
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 · 60 lines · 14 tokens per session scan A 242db995c077
deploy-schema is a command published in the GitHub repository sanity-io/agent-toolkit (180 stars, last pushed 6d ago), licensed MIT. It adds 14 tokens to every session and 337 once invoked, about $0.0001 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 commands, from other repositories
lagune.harden
Apply the defense plan's fixes to the code, safely and one at a time, then record what was applied and what is left. Reads the plan and the charter, then hardens every fix, the fixes, files, or directories you name, or a priority you choose.
goham
End-to-end workflow for working on tasks from a connected Hamster brief. All tasks from the brief are worked on in a single branch, with one PR created at the end.
fix-ci
Detect the current branch's pull request, retrieve its failing CI workflow logs, fix the root causes, commit, and push. This command auto-detects the PR from the current Git branch, fetches check run statuses, downloads failure logs, classifies each failure, implements fixes, and pushes a single commit.
next-task
Intelligently determine and prepare the next action based on comprehensive context.
scaffold-frontend-project
Scaffold a new frontend project following the 5-layer Clean Architecture (Domain, Service, Infrastructure, Presentation, Main).
scaffold-python-package
Scaffold a new Python package following PEP 621, PDM, Black/isort/Flake8, type hints, and Loguru logging.