charlie947/social-media-skills is a collection of markdown instructions that gives AI agents specialized workflows for creating and managing social-media content. It supports a content system spanning LinkedIn, Instagram, Substack, X, and YouTube, with shared voice and context files guiding the individual skills.
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 charlie947/social-media-skills --skill gemini-infographicgit clone --depth 1 https://github.com/charlie947/social-media-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/charlie947/social-media-skills/gemini-infographic)<a href="https://agentmods.dev/skills/charlie947/social-media-skills/gemini-infographic"><img src="https://agentmods.dev/badge/skills/charlie947/social-media-skills/gemini-infographic/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/charlie947/social-media-skills/gemini-infographic"><img src="https://agentmods.dev/badge/skills/charlie947/social-media-skills/gemini-infographic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00093 | $0.00827 |
| Opus 5 | $0.00046 | $0.00413 |
| Sonnet 5 | $0.00019 | $0.00165 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
gemini-infographic 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 13d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gemini-infographic — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini Infographic
CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise the process.
Step 1. Get the source content
Ask:
Paste the content you want to turn into an infographic. A post, newsletter section, blog, research note, or raw bullet points all work.
Wait for the content.
Step 2. Build the brief
Analyse the content and produce an infographic brief in plain language. Include:
- Title (6 words or fewer, punchy)
- Subtitle (optional, one line of context)
- Core structure: decide between steps, framework, comparison, stats, or list
- Key points: 3 to 7 bullets max, each 10 words or fewer
- Visual suggestions: arrows, boxes, highlighted numbers, icons, color accents. Be specific about placement and colour.
- Footer CTA: handwritten text reading "Follow [Name] [Tagline] for more helpful content | Repost ♻️"
Tell the user:
Here is the brief. Tell me what to change, or say "generate" when you're happy.
Wait for approval.
Step 3. Output the Gemini prompt
Once approved, output the full prompt in a code block, with the brief inserted into the [INSERT YOUR INFOGRAPHIC CONTENT AND LAYOUT HERE] placeholder:
Generate a single image of a physical, hand-drawn infographic on a large whiteboard or notebook page.
Crucial Style Instructions (Read First):
Medium: The image must look like a photograph of a real whiteboard or large paper notepad.
Texture: All elements must look created by hand using colored marker pens (black, blue, red, green) and highlighters (yellow/orange). Lines should be slightly imperfect, wobbly, and have the texture of ink on a surface.
No Digital Fonts: All text, headings, and bullet points must appear handwritten or hand-printed in marker pen.
Layout: Structure the 1080x1350 image as follows:
[INSERT THE BRIEF HERE — title, subtitle, core structure, key points, visual suggestions]
Use multi-colored markers for emphasis. Keep text large and legible. Make everything look hand-drawn with slight imperfections. Make it look like a photograph of an actual notebook page.
Always include the handwritten text "Follow [Name] [Tagline] for more helpful content | Repost ♻️" at the bottom of the image, in the same hand-drawn marker style.
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.
- 13d ago First seen · 81 lines · 93 tokens per session scan A c70149ea8de4
gemini-infographic is a skill published in the GitHub repository charlie947/social-media-skills (3,385 stars, last pushed 13d ago), licensed MIT. It adds 93 tokens to every session and 827 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…
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…