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 SkillMedev/social-media-studio --skill social-content-calendargit clone --depth 1 https://github.com/SkillMedev/social-media-studioWrote 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/skillmedev/social-media-studio/social-content-calendar)<a href="https://agentmods.dev/skills/skillmedev/social-media-studio/social-content-calendar"><img src="https://agentmods.dev/badge/skills/skillmedev/social-media-studio/social-content-calendar/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/skillmedev/social-media-studio/social-content-calendar"><img src="https://agentmods.dev/badge/skills/skillmedev/social-media-studio/social-content-calendar.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.00119 | $0.00785 |
| Opus 5 | $0.00060 | $0.00392 |
| Sonnet 5 | $0.00024 | $0.00157 |
| Haiku 4.5 | $0.00012 | $0.00078 |
Grade A, and why
Social Content Calendar 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Social Content Calendar
Turn a brand's pillars, channels, and real calendar into a 4-week multi-platform posting grid that each channel can actually sustain.
Workflow
- Lock pillars and ratio first. Demand 3-5 content pillars before scheduling anything (e.g. education, behind-the-scenes, social proof, product, point-of-view). Apply a default mix of ~40% educational/value, 30% engagement/community, 20% promotional, 10% personality. If the user hands you only promo ideas, push back: feeds over ~25% selling lose reach fast.
- Set per-channel cadence, not one frequency. Default sustainable rates: LinkedIn 3-5x/week (weekday mornings), X 1-3x/day, Instagram 3-5x/week feed plus daily Stories, TikTok 1x/day minimum, YouTube Shorts 3-7x/week. Cap every channel at what the team can hold long-term - 1x forever beats 2x until burnout.
- Anchor to the brand's real dates. Layer in the brand's launches, events, and announcements first, then add only culturally relevant moments. Skip generic holidays unless they fit the brand.
- Reserve reactive capacity. Leave ~20% of slots open for trend/reactive posts; a fully booked calendar can't respond to what's happening.
- Build the grid week by week. Output one table per week with columns: date, platform, pillar, format (carousel/Reel/thread/text/Short), working title, hook angle, CTA, asset needed, status.
- Plan repurposing, don't improvise it. Sequence so a single core idea feeds multiple slots across channels and weeks. Front-load production-heavy formats early in each week.
- Flag capacity and dependencies. Call out posts needing design, video, or approvals; mark which posts block others; note batching opportunities (one shoot, multiple posts).
Quality bar
- Every week's slots map to a named pillar, and the month's pillar mix lands within ~10% of the target ratio.
- Each channel's cadence is justified by that channel's economy, not copied from another.
- Real brand dates appear before any generic cultural moment; ~20% of slots stay open.
- The grid is complete enough to hand to a producer: no slot is missing format, hook, CTA, or asset.
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 · 35 lines · 119 tokens per session scan A 2ece2cb8ef70
Social Content Calendar is a skill published in the GitHub repository SkillMedev/social-media-studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 119 tokens to every session and 785 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-31.
Other skills, from other repositories
Landing Page Copy
Write landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping…
testimonial-capture-interview
Runs customer interviews engineered to produce usable testimonials and case-study raw material - a question sequence that elicits before/after specifics and real numbers, a permission and approval workflow, quote-editing ethics (tighten but never fabricate), and a soundbite extraction procedure. Use when a user says…
Case Study Builder
Turn a customer win into a credible case study - interview-driven raw material, a challenge-solution-results arc, and a quantified results section with real customer quotes. Use when someone asks "write a case study from this customer call", "turn this win into a customer story", "what should I ask the customer in the…
Email Newsletter Pro
Write recurring email newsletters - subject lines that earn the open, preview text that extends them, a body structure readers finish, and cadence rules that keep the list healthy. Use when someone asks "write my newsletter", "give me subject line options", "why is my open rate dropping", "should I send weekly or…
LinkedIn Post Writer
Write LinkedIn posts built for the feed - a hook that survives the two-line truncation, scannable one-idea-per-line structure, a comment-bait close, and first-hour engagement moves. Use when someone asks "write a LinkedIn post about this", "punch up my LinkedIn hook", "why did my post get no reach", or "turn this win…
Tweet Thread Builder
Turn one idea into a tight tweet thread - a hook that earns the click, one beat per post, and momentum to a single CTA. Use when someone asks "turn this into a thread", "write a thread about my launch", "why did my thread flop", or "give me hook options for this". Do NOT use for LinkedIn-format posts - use…