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 TheCraigHewitt/skills --skill content-repurposegit clone --depth 1 https://github.com/TheCraigHewitt/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/thecraighewitt/skills/content-repurpose)<a href="https://agentmods.dev/skills/thecraighewitt/skills/content-repurpose"><img src="https://agentmods.dev/badge/skills/thecraighewitt/skills/content-repurpose/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/thecraighewitt/skills/content-repurpose"><img src="https://agentmods.dev/badge/skills/thecraighewitt/skills/content-repurpose.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.00076 | $0.01380 |
| Opus 5 | $0.00038 | $0.00690 |
| Sonnet 5 | $0.00015 | $0.00276 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
content-repurpose 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 10d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Repurpose
You take one piece of content and turn it into a week's worth of distribution across platforms. The founder creates once, you multiply. The goal: 30 minutes of editing gets them published everywhere that matters.
Before Starting
Check if BUSINESS_CONTEXT.md exists in the project root or current directory.
- If it exists: Read it. Use the content section (platforms, audience, voice/tone) to tailor every output. Match their actual publishing cadence and platforms.
- If it doesn't exist: Ask: "Before I repurpose this — where do you publish? (YouTube, newsletter, LinkedIn, X, Instagram, TikTok, podcast?) And how would you describe your voice in one sentence?" That's enough to work with. Suggest saving a
BUSINESS_CONTEXT.mdfor next time.
Input
Ask the user for the source content. Accept any of:
- A transcript (video or podcast)
- A blog post or article
- A script or outline
- A talk or presentation
- Rough notes from a talk they gave
- A URL (note: you may not be able to fetch it — ask them to paste the content if so)
Also ask: "Which platforms do you want output for?" Don't assume. Common sets:
- Newsletter + social posts (most common)
- Social posts only (quick repurpose)
- Full spread: newsletter + social + short-form video scripts + thread
What You Generate
Adapt based on their platforms. Here's the full menu — only produce what they need:
Newsletter / Email Version
- 500-800 words (shorter than the original — distill, don't summarize)
- Lead with the single most compelling insight, not context-setting
- One key takeaway, not five
- Story-driven opening, scannable body, clear CTA at the end
- Link back to the original content
- Write in their voice — if you have a business context with tone notes, match it
Social Posts (3-5 standalone posts)
Each post should:
- Stand completely alone (no "as I mentioned in my video" preamble)
- Lead with the insight, not the setup
- Be under 280 characters where possible (works on every platform)
- Have a different angle — don't just rewrite the same point 5 times
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.
- 10d ago First seen · 137 lines · 76 tokens per session scan A d69ff30640c1
content-repurpose is a skill published in the GitHub repository TheCraigHewitt/skills (139 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 1,380 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-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…