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 content-experimentation-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/content-experimentation-best-practices)<a href="https://agentmods.dev/skills/vercel-labs/sanity-copilot-eve-template/content-experimentation-best-practices"><img src="https://agentmods.dev/badge/skills/vercel-labs/sanity-copilot-eve-template/content-experimentation-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/content-experimentation-best-practices"><img src="https://agentmods.dev/badge/skills/vercel-labs/sanity-copilot-eve-template/content-experimentation-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.00060 | $0.00342 |
| Opus 5 | $0.00030 | $0.00171 |
| Sonnet 5 | $0.00012 | $0.00068 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
content-experimentation-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 11d 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
98% identical to content-experimentation-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
Content Experimentation Best Practices
Principles and patterns for running effective content experiments to improve conversion rates, engagement, and user experience.
When to Apply
Reference these guidelines when:
- Setting up A/B or multivariate testing infrastructure
- Designing experiments for content changes
- Analyzing and interpreting test results
- Building CMS integrations for experimentation
- Deciding what to test and how
Core Concepts
A/B Testing
Comparing two variants (A vs B) to determine which performs better.
Multivariate Testing
Testing multiple variables simultaneously to find optimal combinations.
Statistical Significance
The confidence level that results aren't due to random chance.
Experimentation Culture
Making decisions based on data rather than opinions (HiPPO avoidance).
References
Start with the reference that matches the current problem, such as design, statistics, CMS integration, or pitfalls. See references/ for detailed guidance:
references/experiment-design.md— Hypothesis framework, metrics, sample size, and what to testreferences/statistical-foundations.md— p-values, confidence intervals, power analysis, Bayesian methodsreferences/cms-integration.md— CMS-managed variants, field-level variants, external platformsreferences/common-pitfalls.md— 17 common mistakes across statistics, design, execution, and interpretation
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.
- 11d ago First seen · 38 lines · 60 tokens per session scan A 3bfc88457e2c
content-experimentation-best-practices is a skill published in the GitHub repository vercel-labs/sanity-copilot-eve-template (5 stars, last pushed 22d ago), licensed MIT. It adds 60 tokens to every session and 342 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to content-experimentation-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.