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 shawnpang/startup-founder-skills --skill social-contentgit clone --depth 1 https://github.com/shawnpang/startup-founder-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/shawnpang/startup-founder-skills/social-content)<a href="https://agentmods.dev/skills/shawnpang/startup-founder-skills/social-content"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/social-content/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/shawnpang/startup-founder-skills/social-content"><img src="https://agentmods.dev/badge/skills/shawnpang/startup-founder-skills/social-content.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.00057 | $0.01682 |
| Opus 5 | $0.00028 | $0.00841 |
| Sonnet 5 | $0.00011 | $0.00336 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
social-content 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 12d 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:
- social-content — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Social Content
When to Use
- Building a LinkedIn authority or thought leadership system from scratch.
- Defining content pillars and weekly posting rhythm.
- Writing individual posts with strong hooks.
- Creating a content calendar with real dates and ready-to-write hooks.
- Establishing positioning before content creation begins.
- Reviewing 30-day performance and adjusting content ratios.
Context Required
From startup-context or the user:
- Positioning statement — Your one-liner: who you help, what you do, how you are different. If the user lacks this, help them clarify it before building a content system.
- Target audience — Specific titles, company stages, industries on LinkedIn
- Historical performance — Past posting data, what worked, what fell flat (if any)
- Content goal — Leads, job opportunities, speaking invitations, partnerships, or community
- Time commitment — Realistic weekly hours available for content creation and engagement
A critical gate: positioning clarity must come first. An unfocused content system produces unfocused results. If the user cannot articulate who they serve and why they are different, address that before building pillars.
Workflow
- Clarify positioning — Confirm or develop the user's one-liner. This is the foundation. Every pillar, hook, and post must connect back to this positioning.
- Select mode based on need:
- Quick: 3 content pillars + 1-week starter plan (for getting unstuck)
- Standard: Full system with pillars, formats, rhythm, and first week of posts written (default)
- Deep: Complete 90-day calendar with 10 written posts and engagement strategy
- Build content pillars — Each pillar must satisfy four criteria:
- You have genuine expertise in this area
- Your target audience genuinely cares about this topic
- You can sustain 6+ months of content on this pillar
- It connects to your revenue or stated objective
- Allocate pillar ratios:
- 70% core expertise — Authority-building content that demonstrates deep knowledge
- 20% adjacent insights — Differentiation content connecting your expertise to unexpected areas
- 10% personal content — Relatability, behind-the-scenes, founder journey
- Assign format strategy per pillar:
- Story posts — Drive connection and high engagement through narrative tension and personal insight
- Framework/list posts — Establish authority and credibility through structured thinking
- Case studies — Build trust through proof and results
- Hot takes — Generate visibility through informed contrarian opinions
- Behind-the-scenes — Create relatability and relationship depth
- Recommended weekly mix: 2-3 frameworks, 1-2 stories, 1 proof point
- Build the calendar — Use actual dates (YYYY-MM-DD), not generic placeholders. Provide 4-week calendars with real hooks ready for immediate writing. Include 5 starter post hooks to eliminate blank-page paralysis.
- Write the first batch — For standard and deep modes, write complete posts with hooks, body, and CTAs. Posts should be 150-300 words, short paragraphs (1-2 sentences), end with a question or discussion prompt.
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.
- 12d ago First seen · 117 lines · 57 tokens per session scan A dd570005a7f7
social-content is a skill published in the GitHub repository shawnpang/startup-founder-skills (321 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 1,682 once invoked, about $0.0003 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…