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 writing-qualitygit 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/writing-quality)<a href="https://agentmods.dev/skills/vercel-labs/sanity-copilot-eve-template/writing-quality"><img src="https://agentmods.dev/badge/skills/vercel-labs/sanity-copilot-eve-template/writing-quality/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/writing-quality"><img src="https://agentmods.dev/badge/skills/vercel-labs/sanity-copilot-eve-template/writing-quality.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.00073 | $0.00555 |
| Opus 5 | $0.00036 | $0.00278 |
| Sonnet 5 | $0.00015 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
writing-quality 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.
How it starts
The opening of the file, as written. The whole thing — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Quality
House-neutral rules for making drafted content read like a person wrote it. They apply to any prose surface. Layer project- or brand-specific voice guidance on top of them.
When to Apply
Load this skill before:
- Drafting new content (a blog post, landing-page copy, a Notion draft, release notes)
- Editing or rewriting existing content
- Reviewing a draft before proposing it to the user
Core Rules
- Kill the AI tells: em-dash overuse, "delve", "leverage", "it's not just X, it's Y", rule-of-three padding, and the rest of the patterns in
references/ai-phrases-to-avoid.md. - Prefer plain English. Swap bloated or vague wording for the shorter, concrete alternative.
references/plain-english-alternatives.mdis the lookup table. - Front-load the point. Lead sentences, paragraphs, and sections with the conclusion, because readers scan.
- Concrete over abstract. Show an example before stating a principle, and cut hedges like "just", "simply", "very", and "really".
- Match the user's voice, not a default. When editing existing content, keep its register and conventions. These rules trim the noise; they don't impose a personality.
References
Load the reference that matches the task rather than all of them at once:
references/ai-phrases-to-avoid.md: words, phrases, and punctuation patterns that mark text as AI-generated, with replacements. Load when drafting or editing any prose.references/plain-english-alternatives.md: plain-English swaps for corporate, padded, or vague wording. Load when drafting or editing any prose.references/web-writing-best-practices.md: a sourced checklist for long-form web content, covering scanning behavior, hooks, structure, readability, length by intent, SEO basics, and closes. Load when writing or restructuring articles, blog posts, or guides.references/web-content-specs.md: the concrete numbers behind that checklist (slug rules, heading cadence, readability thresholds, word count by intent, alt text, internal links). Load for a final spec check on a piece. Title, meta, and Open Graph specs live in theseo-aeo-best-practicesskill.
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 · 31 lines · 73 tokens per session scan A 079d7e85aaaa
writing-quality is a skill published in the GitHub repository vercel-labs/sanity-copilot-eve-template (5 stars, last pushed 22d ago), licensed MIT. It adds 73 tokens to every session and 555 once invoked, about $0.0004 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-31.
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.