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/moses607/socialforge/campaign-buildernpx skills add moses607/socialforge --skill campaign-buildergit clone --depth 1 https://github.com/moses607/socialforgeWhat 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.00115 | $0.01157 |
| Opus 5 | $0.00057 | $0.00579 |
| Sonnet 5 | $0.00023 | $0.00231 |
| Haiku 4.5 | $0.00012 | $0.00116 |
Grade A, and why
campaign-builder 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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Builder
A campaign is a story with a deadline, not a pile of promo posts. Audiences buy at the peak of desire, and desire is manufactured through sequenced beats — anticipation before availability, urgency at the close. First-principles: warm the audience before you ask, escalate the CTA from soft to hard so no one feels ambushed, and stack scarcity at the end where it converts. The plan below turns any launch into a three-act arc with defined beats and a metric per phase so you know if it's working before the cart opens.
1. Pre-launch — manufacture anticipation (7-14 days)
- Tease the problem, not the product. Post the pain your offer solves; agitate it. No selling yet.
- Open a waitlist / early-access list. Trade a lead magnet or "first + cheapest" promise for the email/DM. This is your launch-day fuel.
- Seed proof and story. Share the origin, the beta results, behind-the-scenes of building it.
- Run a countdown mechanic in the final 3 days: "3 days until X" posts + Stories with a reminder sticker.
- Metric: waitlist size + reply/DM rate. A cold audience won't warm on launch day — grow the list here or the launch stalls.
2. Launch — daily beats + CTA ladder (3-7 days, cart open)
Escalate the CTA from soft to hard across the window:
- Open (soft): "It's live. Here's what it is and who it's for." Link/CTA once.
- Value + demo: show it working; a mini-win or free sample. CTA: "See how it works."
- Proof day: testimonials, case study, results screenshots. CTA: "Join them."
- Objection crush: FAQ, guarantee, "is this for me?" CTA: direct.
- Urgency (hard): "Price rises / bonus disappears in 48h." Real deadline only.
- Final call: "Closes tonight." Multiple posts + Stories + an email. Expect 30-50% of sales here.
- Metric: CTR, add-to-cart, conversion rate, revenue per beat. Watch which beat sells — double it next launch.
3. Post-launch — nurture + repurpose (7-14 days)
- Onboard + deliver a fast win so new buyers succeed and refer.
- Sell the non-buyers softly: a downsell, waitlist for next round, or "doors reopen" list.
- Repurpose the campaign: best-performing beats become evergreen content; testimonials feed the next pre-launch.
- Debrief: log open/close numbers, best beat, biggest objection.
- Metric: fulfillment/refund rate, referral rate, list growth for next launch.
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.
- 2d ago First seen · 68 lines · 115 tokens per session scan A c14cd2e709e5
campaign-builder is a skill published in the GitHub repository moses607/socialforge (2 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 1,157 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
blog
Full-lifecycle blog engine with 31 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents. Routes user requests to the right sub-skill: writing, rewriting, analysis, outlines, audits, schema, charts, images, repurposing, AI citation SEO, FLOW framework prompts, topic-cluster…
blog-write
Write new blog articles from scratch optimized for Google rankings and AI citations. Generates full articles with template selection, answer-first formatting, Key Takeaways summary box, information gain markers, citation capsules, sourced statistics, Pixabay/Unsplash images, built-in SVG chart generation, optional FAQ…
blog-brief
Generate detailed content briefs for blog posts with target keywords, content outlines, competitive analysis, recommended statistics, image and chart suggestions, word count targets, internal linking architecture, template recommendations (12 types), TL;DR drafts, citation capsule planning, information gain prompts…
blog-geo
AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together. Use whenever the user wants their content to rank or be cited in ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com, Google AI Overviews, or Google AI Mode. AI citation optimization audit scoring blog posts…
blog-cannibalization
Detect keyword cannibalization across blog posts by extracting primary keywords from titles and headings, clustering semantically similar targets, and flagging posts competing for the same search intent. Supports local-only mode (grep-based) and DataForSEO API mode (Page Intersection endpoint at $0.01/call). Outputs…
blog-schema
Generate complete JSON-LD schema markup for blog posts with Article/BlogPosting, Person, Organization, BreadcrumbList, ImageObject, and optional FAQPage. Validates against Google requirements and warns about deprecated types. Use when user says "schema", "blog schema", "json-ld", "structured data", "schema markup"…