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 Ootto-AI/claude-content-skills --skill creator-outreachgit clone --depth 1 https://github.com/Ootto-AI/claude-content-skillsWrote 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/ootto-ai/claude-content-skills/creator-outreach)<a href="https://agentmods.dev/skills/ootto-ai/claude-content-skills/creator-outreach"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-content-skills/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/ootto-ai/claude-content-skills/creator-outreach"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-content-skills/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.00107 | $0.00642 |
| Opus 5 | $0.00053 | $0.00321 |
| Sonnet 5 | $0.00021 | $0.00128 |
| Haiku 4.5 | $0.00011 | $0.00064 |
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creator Outreach
Write outreach that proves the operator has done the work: it is relevant to the creator, clear about the ask, and easy to decline.
1. Confirm permission and fit
Record the creator's supplied or public business contact route, the reason the collaboration is relevant, the approved offer, and the required disclosure or compensation terms. Do not contact a creator merely because they are in a large list. If the relationship is not mutually useful, stop before drafting.
2. Find one honest personalisation point
Use a specific, recent piece of work or audience need that the operator can accurately name. Explain the connection in one sentence without flattery theatre or invented familiarity. Never imply that the creator uses the product, knows the team, or endorsed anything.
3. Make the ask inspectable
State what the collaboration could involve, the creative latitude, compensation or consideration where approved, timeline, disclosure expectation, and the smallest next step. Link only to material the creator needs to evaluate the proposal. Make a no-pressure decline simple.
4. Follow up with restraint
Record the outreach date and one reasonable follow-up point. If there is no response, do not escalate through other personal channels, pressure the creator, or treat silence as consent. Update the partnership record with a factual outcome so future outreach does not repeat unwanted contact.
Hard rules
- Never automate unsolicited replies, DMs, or follow-ups.
- Do not misrepresent the sender, relationship, compensation, product access, or urgency.
- Use only appropriate contact details supplied for business contact or already approved by the operator.
- Do not promise results, creative approval, or payment terms that are not authorised.
- Include required sponsorship, gifted, affiliate, or material-connection disclosures in the later brief, not as a hidden condition.
Failure modes
| Failure | Do this instead |
|---|---|
| The message could be sent to anyone | Add one verifiable relevance point or do not send it. |
| The ask hides the commercial terms | State the available terms clearly or say they are still being scoped. |
| Follow-up becomes harassment | Set one follow-up and close the record after no response. |
| Outreach starts before partnership fit | Return to influencer-partnerships and evaluate the collaboration first. |
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 · 46 lines · 107 tokens per session scan A 1ad584daa5c9
creator-outreach is a skill published in the GitHub repository Ootto-AI/claude-content-skills (30 stars, last pushed 20d ago), licensed MIT. It adds 107 tokens to every session and 642 once invoked, about $0.0005 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
scrapecreators-api
Scrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API. Covers TikTok, Instagram, YouTube, LinkedIn, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, TikTok Shop, Google, and link-in-bio services (Linktree, Komi, Pillar, Linkbio…
outlier-post-finder
Use when the user wants to find posts, videos, reels, shorts, tweets, or social content that overperformed versus a creator, brand, or competitor baseline. Finds outliers, explains why they worked, extracts hooks and formats, and produces a practical swipe file.
ad-library-teardown
Use when the user wants to analyze active ads from Meta/Facebook, Google, or LinkedIn ad libraries; tear down a competitor's messaging; extract hooks, offers, CTAs, video transcripts, landing page claims, and test ideas from public ads.
comment-mining
Use when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos.
competitor-social-research
Use when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a practical social strategy brief from public social data.
transcript-intelligence
Use when the user wants to summarize, analyze, or repurpose transcripts from TikTok, Instagram, YouTube, Facebook, X/Twitter, LinkedIn, Rumble, or Reddit video posts. Extracts hooks, claims, quotes, content atoms, themes, and reusable scripts.