vercel-labs/marketing-team-eve-template is a deployable team of AI marketing agents led by a coordinating agent that delegates launches, writing, and conversion work to specialists. Teams use it through Slack or a terminal to create blog drafts, social posts, and email campaigns in Notion, Typefully, and Resend, with approval required for irreversible actions. The catalogue skills and instructions define workflows for using this marketing team.
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/marketing-team-eve-template --skill brand-contextgit clone --depth 1 https://github.com/vercel-labs/marketing-team-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/marketing-team-eve-template/brand-context)<a href="https://agentmods.dev/skills/vercel-labs/marketing-team-eve-template/brand-context"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/brand-context/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/marketing-team-eve-template/brand-context"><img src="https://agentmods.dev/badge/skills/vercel-labs/marketing-team-eve-template/brand-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 35 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00037 | $0.00749 |
| Opus 5 | $0.00018 | $0.00375 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
brand-context 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 13d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The brand context document
This is the document every specialist loads at the start of every task. That makes it the highest-leverage thing you write and the easiest to ruin, in two directions: too thin and everyone guesses, too long and everyone pays for it on every delegation.
Write it as a briefing for a competent colleague who has never seen the product. Not a manifesto, not an archive.
What goes in
Six sections, in this order, because that's roughly the order a reader needs them.
- What the product is. Two or three sentences, plain, no category jargon. What it does and what it replaces.
- Who it's for. The primary segment, specifically enough to predict a problem and a buyer. Secondary segments named as secondary.
- Positioning. The alternative you beat, the differentiators worth claiming, and the proof for each.
- Messaging. The core message and the three or four pillars, each with its proof and its grade.
- Voice. How the team writes, with two or three real examples, and the phrases that are off-limits.
- Open questions. What isn't settled, and what would settle it.
Section 6 is the one people delete and the one that earns its place. It's how a specialist knows to hedge a claim rather than assert it.
What stays out
- Campaign and task detail. A launch brief, this quarter's theme, a specific piece's angle. Those belong in the delegation that needs them. Everything in this document is read by every task, so anything task-specific is a cost paid many times for one use.
- Long-form source material. Interview transcripts, full competitor teardowns, the complete messaging framework. Store those as assets and reference them.
- Anything you can't support. An aspiration written as a fact will be published as a fact by someone downstream.
- Preferences about how a person likes to work. Those live in the per-user preferences document, not here. This document describes the product, not the reader.
Length
Keep it to a page or two. The size cap in the tool is a backstop, not a target.
What ships with it
1 file 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.
- 13d ago First seen · 52 lines · 37 tokens per session scan A 77cfdc9bfa87
brand-context is a skill published in the GitHub repository vercel-labs/marketing-team-eve-template (436 stars, last pushed 23d ago), licensed MIT. It adds 37 tokens to every session and 749 once invoked, about $0.0002 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 skills, from other repositories
writing-quality
Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill…
portable-text-serialization
Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown…
portable-text-conversion
Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers…
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content…
content-experimentation-best-practices
Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or…