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 post-bridge-hq/agent-mode --skill b2c-organic-social-media-marketinggit clone --depth 1 https://github.com/post-bridge-hq/agent-modeWrote 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/post-bridge-hq/agent-mode/b2c-organic-social-media-marketing)<a href="https://agentmods.dev/skills/post-bridge-hq/agent-mode/b2c-organic-social-media-marketing"><img src="https://agentmods.dev/badge/skills/post-bridge-hq/agent-mode/b2c-organic-social-media-marketing/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/post-bridge-hq/agent-mode/b2c-organic-social-media-marketing"><img src="https://agentmods.dev/badge/skills/post-bridge-hq/agent-mode/b2c-organic-social-media-marketing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 210 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00078 | $0.03064 |
| Opus 5 | $0.00039 | $0.01532 |
| Sonnet 5 | $0.00016 | $0.00613 |
| Haiku 4.5 | $0.00008 | $0.00306 |
Grade A, and why
b2c-organic-social-media-marketing 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 8d 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
B2C Marketing, Short-Form Video Content Machine
What this skill does, and does not do. It is advisory. It coaches you through account creation, warmup, content-market fit, hooks, CTAs and scaling decisions. It does not run local commands, does not process media on your machine, does not move or delete your files, and does not schedule background jobs. Where posting automation is genuinely useful (Phase 6, once formats are proven) it points at a separate companion skill, so posting capability is something you opt into on purpose rather than something this skill assumes.
Based on the system that generated 500M+ views, 130K+ downloads, and $33K+ revenue from organic content alone. No ads. No budget.
Your Role
You are both an execution engine and a growth coach. You don't just post content, you guide the user through the entire organic growth journey, from account creation to scaling across platforms. When the user is stuck, coach them. When they have content ready, post it. Always be pushing toward the next milestone.
Coaching Workflow
Determine what the user needs, then route:
- New to organic growth / starting fresh? Assess their product, then walk through the phases below in order.
- Already posting but not getting views? Diagnose: they likely skipped the warmup phase or have not found content-market fit.
- Getting views but not conversions? Audit the funnel: bio, CTAs, whether the content attracts their ICP.
- Ready to scale? Verify the readiness milestones in Phase 6 before agreeing.
Phase 1: Account Creation (Day 1)
Help the user create brand new TikTok and Instagram accounts dedicated to their app or business.
Key rules
- Use a different email for each account if possible (same email works but is not ideal)
- Set up as a business or creator account on Instagram (enables bio links)
- TikTok does not allow links on new accounts, so type the URL or app name in the bio instead
Bio that converts. The bio must tell visitors what you offer and how to get it. Every view that hits the profile should know exactly what to do next.
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.
- 8d ago Changed · +33 lines d2124879dd44
- 12d ago First seen · 237 lines · 78 tokens per session scan A d934945c4034
b2c-organic-social-media-marketing is a skill published in the GitHub repository post-bridge-hq/agent-mode (17 stars, last pushed 3d ago), licensed MIT. It adds 78 tokens to every session and 3,064 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…
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…