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 synthesisengineering/synthesis-skills --skill synthesis-content-distributiongit clone --depth 1 https://github.com/synthesisengineering/synthesis-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/synthesisengineering/synthesis-skills/synthesis-content-distribution)<a href="https://agentmods.dev/skills/synthesisengineering/synthesis-skills/synthesis-content-distribution"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-content-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/synthesisengineering/synthesis-skills/synthesis-content-distribution"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-content-distribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00108 | $0.04960 |
| Opus 5 | $0.00054 | $0.02480 |
| Sonnet 5 | $0.00022 | $0.00992 |
| Haiku 4.5 | $0.00011 | $0.00496 |
Grade A, and why
synthesis-content-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 11d 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Distribution
Strategically promote content across social media platforms to build genuine thought leadership, spark meaningful discussion, and create valuable professional connections.
Initial Analysis Phase
When given a content URL, produce a strategic brief before writing any posts:
Content Analysis
- Core insight or argument
- Primary value proposition for different audiences
- Natural discussion hooks and controversy points
- Connection to current industry conversations
- Unique angles or perspectives presented
Audience Mapping
- Who benefits most from this content
- What specific problems it solves or questions it answers
- Which professional communities find it most relevant
- Potential objections or counterarguments to anticipate
Platform Strategy Recommendation
- Which platforms are optimal for this content (and why)
- Suggested posting sequence and timing
- Platform-specific angles to emphasize
- Communities or groups to target
- Risks or sensitivities to navigate
Voice and Positioning
- How this content advances thought leadership
- What authority or expertise it demonstrates (implicitly)
- Connections to other work or ongoing themes
- How to frame without sounding promotional
Present this analysis and get feedback before writing posts.
Content Information Template
Gather this information:
- Content URL
- Content Type: Blog post, published article, research/analysis, opinion piece, tutorial/guide, case study, or other
- Primary Goal: Establish expertise, generate discussion, drive qualified traffic, create speaking/advising opportunities, test ideas with peers, build relationships, or other
- Timing Considerations: Current events ties, relevant industry discussions, upcoming events, time-sensitive elements
- Constraints or Sensitivities: Topics to avoid, relationships to navigate, competitive sensitivities
Strategic Context and Voice
Voice and tone for posts come from the user's active voice profile, not from this skill. Apply whatever voice profile is loaded in the current environment — typically a private skill (e.g., <workspace>-private-writing-voice), a CLAUDE.md / AGENTS.md instruction block, or both. This skill is methodology-agnostic about voice; it does not embed sample voice traits, sample forbidden language, or persona text.
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.
- 11d ago First seen · 437 lines · 108 tokens per session scan A 765facccdc04
synthesis-content-distribution is a skill published in the GitHub repository synthesisengineering/synthesis-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 108 tokens to every session and 4,960 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
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…