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 agentmods add skills/fergupa/claude_plugins/content-creationnpx skills add fergupa/claude_plugins --skill content-creationgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/content-creation)<a href="https://agentmods.dev/skills/fergupa/claude_plugins/content-creation"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/content-creation.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.02040 |
| Opus 5 | $0.00028 | $0.01020 |
| Sonnet 5 | $0.00011 | $0.00408 |
| Haiku 4.5 | $0.00006 | $0.00204 |
Grade A, and why
content-creation 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 yesterday.
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.
This is a copy
97% identical to content-creation — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Creation Skill
Guidelines and frameworks for creating effective marketing content across channels.
Content Type Templates
Blog Post Structure
- Headline — clear, benefit-driven, includes primary keyword (aim for 60 characters or less for SEO)
- Introduction (100-150 words) — hook the reader with a question, statistic, bold claim, or relatable scenario. State what the post will cover. Include primary keyword.
- Body sections (3-5 sections) — each with a descriptive subheading (H2). Use H3 for subsections. One core idea per section with supporting evidence, examples, or data.
- Conclusion (75-100 words) — summarize key takeaways, reinforce the main message, include a call to action.
- Meta description — under 160 characters, includes primary keyword, compels the click.
Social Media Post Structure
- Hook — first line grabs attention (question, bold statement, number)
- Body — 2-4 concise points or a short narrative
- CTA — what should the reader do next (comment, click, share, tag)
- Hashtags — 3-5 relevant hashtags (platform-dependent)
Email Newsletter Structure
- Subject line — under 50 characters, creates curiosity or states clear value
- Preview text — complements the subject line, does not repeat it
- Header/hero — visual anchor and one-line value statement
- Body sections — 2-3 content blocks, each scannable with a bold intro sentence
- Primary CTA — one clear action per email
- Footer — unsubscribe link, company info, social links
Landing Page Structure
- Headline — primary benefit in under 10 words
- Subheadline — elaborates on the headline with supporting context
- Hero section — headline, subheadline, primary CTA, supporting image or video
- Value propositions — 3-4 benefit-driven sections with icons or images
- Social proof — testimonials, logos, stats, case study snippets
- Objection handling — FAQ or trust signals
- Final CTA — repeat the primary call to action
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.
- yesterday First seen · 157 lines · 56 tokens per session scan A e0145f84827b
content-creation is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 2,040 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to content-creation, differing in 1 line, and is treated as a copy.
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…