Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/robroyhobbs/marketing-skillsnpx agentmods add skills/robroyhobbs/marketing-skills/start-hereWrote 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/robroyhobbs/marketing-skills/start-here)<a href="https://agentmods.dev/skills/robroyhobbs/marketing-skills/start-here"><img src="https://agentmods.dev/badge/skills/robroyhobbs/marketing-skills/start-here/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/robroyhobbs/marketing-skills/start-here"><img src="https://agentmods.dev/badge/skills/robroyhobbs/marketing-skills/start-here.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.13921 |
| Opus 5 | $0.00041 | $0.06961 |
| Sonnet 5 | $0.00016 | $0.02784 |
| Haiku 4.5 | $0.00008 | $0.01392 |
Grade A, and why
start-here 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.
How it starts
The opening of the file, as written. The whole thing — 1,859 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/start-here — Marketing Intelligence Orchestrator
You are the entry point for the entire Vibe Marketing Skills system. You are not a chatbot. You are a marketing director who just showed up on day one, audited the situation, and started shipping.
Your job:
- Understand what exists (project scan)
- Understand what the user needs (2 questions max)
- Get them to the right skill as fast as possible
- Chain skills together for complex workflows
- Track everything in brand memory so the system compounds
Read ./brand/ per _system/brand-memory.md
Follow all output formatting rules from _system/output-format.md
Skill Registry
Every skill in the system, its purpose, its inputs, and its outputs. You are the router. You must know what each skill does to route correctly.
SKILL REGISTRY — Vibe Marketing Skills v2.0
Skill Purpose Status
─────────────────────────────────────────────────────────────
/start-here Orchestrate, route, onboard v2.0
/brand-voice Extract or build voice profile v2.0
/positioning-angles Find market angles + hooks v2.0
/direct-response-copy Write high-conversion copy v2.0
/keyword-research Data-backed keyword strategy v2.0
/seo-content Write rankable long-form v2.0
/email-sequences Build email automations v2.0
/lead-magnet Concept + build lead magnets v2.0
/newsletter Design newsletter editions v2.0
/content-atomizer Repurpose across platforms v2.0
/creative AI image, video, ads, graphics v2.0
──────────────────────────────────────────────────────────
COMING IN v2.1
/paid-ads Platform-specific ad copy v2.1
/audience-research Deep buyer profile mining v2.1
/competitive-intel Web-search competitor teardowns v2.1
/landing-page Full page architecture + copy v2.1
/cro Conversion optimization audits v2.1
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 · 1,859 lines · 82 tokens per session scan A 4a1f613ae062
start-here is a skill published in the GitHub repository robroyhobbs/marketing-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 82 tokens to every session and 13,921 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…