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 cross-platform-distributiongit 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/cross-platform-distribution)<a href="https://agentmods.dev/skills/ootto-ai/claude-content-skills/cross-platform-distribution"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-content-skills/cross-platform-distribution/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/cross-platform-distribution"><img src="https://agentmods.dev/badge/skills/ootto-ai/claude-content-skills/cross-platform-distribution.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.00113 | $0.00651 |
| Opus 5 | $0.00056 | $0.00326 |
| Sonnet 5 | $0.00023 | $0.00130 |
| Haiku 4.5 | $0.00011 | $0.00065 |
Grade A, and why
cross-platform-distribution 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.
Cross-Platform Distribution
Give one approved message different jobs across channels so distribution increases useful reach without turning into noisy duplication.
1. Start with a locked source
Ask for the approved campaign brief or source asset, its audience, claim boundary, action, timing, and available formats. If the message is not approved, stop and route to campaign-brief or positioning-audit. Do not turn an untested idea into a distribution plan.
2. Assign channel roles
For every proposed channel, state the audience context, what that channel should contribute, the format it can support, and the action it should earn. A channel may educate, create discussion, provide proof, reach partners, or send qualified traffic. Exclude channels with no clear role rather than filling a grid.
3. Adapt the mechanism, not the truth
Translate the same approved point into channel-native openings, structure, visual requirements, and conversation prompts. Keep the claim, proof, and action consistent. Note what cannot move across: private examples, unsupported performance claims, or assets with rights limited to another platform.
4. Sequence and measure
Order releases so early posts can inform later ones without waiting for a false certainty. Specify cadence, owner, links or UTMs where applicable, and the measurement that each channel is meant to influence. End with the decision that determines whether to extend, revise, or stop distribution.
Hard rules
- Never paste the same post across platforms without adapting the format and context.
- Do not add channels merely because they are popular or have a large theoretical audience.
- Preserve every approved claim boundary and disclosure requirement.
- Do not use UTM links where the destination or tracking convention has not been approved; use utm-campaign-plan first.
- Keep paid, owned, creator, and community activity labelled separately.
Failure modes
| Failure | Do this instead |
|---|---|
| One asset becomes five duplicate posts | Give each channel a distinct audience job and angle. |
| Format is chosen before audience context | Start with the role, then choose the smallest suitable format. |
| A weak post is endlessly republished | Set a review point and change the message or stop based on evidence. |
| Links cannot be attributed | Create an approved UTM plan before publishing trackable links. |
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 · 113 tokens per session scan A 32904fa684b5
cross-platform-distribution is a skill published in the GitHub repository Ootto-AI/claude-content-skills (30 stars, last pushed 19d ago), licensed MIT. It adds 113 tokens to every session and 651 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-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.
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.
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.
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.