Sanity Copilot eve Template is a Slack-based assistant that lets team members query and edit Sanity content, inspect schemas, manage drafts and releases, and send long-form drafts to Notion. Teams use it to work on Sanity projects through Slack with each person's permissions and approval controls for sensitive actions. The catalogue add-ons support this agent workflow.
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 skills add vercel-labs/sanity-copilot-eve-template --skill seo-aeo-best-practicesgit clone --depth 1 https://github.com/vercel-labs/sanity-copilot-eve-templateWrote 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.
[](https://agentmods.dev/skills/vercel-labs/sanity-copilot-eve-template/seo-aeo-best-practices)<a href="https://agentmods.dev/skills/vercel-labs/sanity-copilot-eve-template/seo-aeo-best-practices"><img src="https://agentmods.dev/badge/skills/vercel-labs/sanity-copilot-eve-template/seo-aeo-best-practices/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.
<a href="https://agentmods.dev/skills/vercel-labs/sanity-copilot-eve-template/seo-aeo-best-practices"><img src="https://agentmods.dev/badge/skills/vercel-labs/sanity-copilot-eve-template/seo-aeo-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00082 | $0.00397 |
| Opus 5 | $0.00041 | $0.00198 |
| Sonnet 5 | $0.00016 | $0.00079 |
| Haiku 4.5 | $0.00008 | $0.00040 |
Grade A, and why
seo-aeo-best-practices 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 12d 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.
This is a copy
97% identical to seo-aeo-best-practices — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
SEO & AEO Best Practices
Principles for optimizing content for both traditional search engines (SEO) and AI-powered answer engines (AEO). Includes Google's EEAT guidelines and structured data implementation.
When to Apply
Reference these guidelines when:
- Implementing metadata and Open Graph tags
- Creating sitemaps and robots.txt
- Adding JSON-LD structured data
- Optimizing content for featured snippets
- Preparing content for AI assistants (ChatGPT, Perplexity, etc.)
- Evaluating content quality using EEAT principles
Core Concepts
SEO (Search Engine Optimization)
Optimizing content to rank well in traditional search results (Google, Bing).
AEO (Answer Engine Optimization)
Optimizing content to be selected as authoritative answers by AI systems.
EEAT (Experience, Expertise, Authoritativeness, Trustworthiness)
Google's framework for evaluating content quality.
References
Start with the one reference that matches the task, such as technical SEO, structured data, EEAT, or AI-answer readiness. See references/ for detailed guidance:
references/eeat-principles.md— EEAT implementation and author schemareferences/structured-data.md— JSON-LD patterns (Article, FAQ, Breadcrumb, Product)references/technical-seo.md— Technical SEO checklist (metadata, sitemaps, hreflang, robots.txt)references/aeo-considerations.md— AI/AEO considerations (AI Overviews, crawler management)
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 36 lines · 82 tokens per session scan A 6cff03d87bc9
seo-aeo-best-practices is a skill published in the GitHub repository vercel-labs/sanity-copilot-eve-template (5 stars, last pushed 23d ago), licensed MIT. It adds 82 tokens to every session and 397 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to seo-aeo-best-practices, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
deliverability
Use when the question is whether email will reach the inbox, covering sending domain setup, authentication, list hygiene, complaint and bounce rates, or a drop in delivery.
email-adaptation
Use when turning existing copy, a blog post, an announcement, or a brief into an email that works in an inbox, including deciding what to cut and what to link out to.
resend-build
Use when building, editing, or sending anything in Resend, including broadcasts, templates, segments, and contacts, or when checking what a past send did.
email-style
Use when writing or editing the copy of an email, newsletter, or broadcast in the house voice, including subject lines and preview text.
brand-context
Use before writing or updating the team's shared brand context document: what belongs in it, how it's structured, how to merge new information without losing what's there, and what to keep out.
customer-research
Use when you need to find out what customers actually think rather than assume it: what to ask in an interview, how to mine language from reviews and support conversations, and how to tell a real finding from a polite one.