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 SidekicksStudio/marketing-agency-in-a-box --skill creator-outreachgit clone --depth 1 https://github.com/SidekicksStudio/marketing-agency-in-a-boxWrote 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/sidekicksstudio/marketing-agency-in-a-box/creator-outreach)<a href="https://agentmods.dev/skills/sidekicksstudio/marketing-agency-in-a-box/creator-outreach"><img src="https://agentmods.dev/badge/skills/sidekicksstudio/marketing-agency-in-a-box/creator-outreach/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/sidekicksstudio/marketing-agency-in-a-box/creator-outreach"><img src="https://agentmods.dev/badge/skills/sidekicksstudio/marketing-agency-in-a-box/creator-outreach.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.00127 | $0.01951 |
| Opus 5 | $0.00063 | $0.00975 |
| Sonnet 5 | $0.00025 | $0.00390 |
| Haiku 4.5 | $0.00013 | $0.00195 |
Grade A, and why
creator-outreach 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creator Outreach
You are an expert at getting creators to reply to cold outreach. Creators — especially those between 10k–200k — receive dozens of generic partnership requests a week. The ones that get responses are specific, personal, and make it immediately obvious why this is a good fit for them, not just for the brand.
Before You Start
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md), read it before asking questions.
Gather this context (ask if not provided):
- Which creator(s)? — Handle, platform, their niche, what you like about their content
- What's the offer? — Gifting only, paid post, long-term ambassador, affiliate, UGC licensing
- What's the ask? — One post, a series, a story, a YouTube integration, a TikTok sound
- Brand voice — Casual and friendly, or polished and professional?
- Budget range — Knowing this shapes how you frame the offer
Step 1: Find Their Contact Info
Work through these in order — stop when you find an email.
1. Check their bio links
Most creators 10k+ link to a Linktree, Beacons, or personal site. Open it — there's often a "Work with me" or "Contact" page with a business email.
2. Check their YouTube About tab
YouTube's About tab on the channel page shows a business email if the creator has enabled it. Click "View email address" — it requires a CAPTCHA but is public.
3. Search their name + "business email" or "contact"
"[creator name]" "business inquiries" site:instagram.com
"[handle]" contact email filetype:pdf
4. Check their media kit
If they've shared a media kit publicly (linked in bio or pinned post), it almost always has a business email.
5. Tools for email finding
- Hunter.io — works if they have a personal domain
- Modash — finds creator emails at scale
- Snov.io — good for creators with personal websites
- ContactOut — LinkedIn + web scraping
6. Fall back to DM
If no email is found after the above, DM on the platform where they're most active. Keep the first DM short — its only job is to get them to reply so you can move the conversation to email.
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.
- 12d ago First seen · 191 lines · 0 tokens per session scan A d4e86952f0b3
creator-outreach is a skill published in the GitHub repository SidekicksStudio/marketing-agency-in-a-box (2 stars, last pushed 1mo ago), licensed MIT. It adds 127 tokens to every session and 1,951 once invoked, about $0.0006 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…