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 b2bforce/b2bforce --skill marketing-content-linkedin-postgit clone --depth 1 https://github.com/b2bforce/b2bforceWrote 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/b2bforce/b2bforce/marketing-content-linkedin-post)<a href="https://agentmods.dev/skills/b2bforce/b2bforce/marketing-content-linkedin-post"><img src="https://agentmods.dev/badge/skills/b2bforce/b2bforce/marketing-content-linkedin-post.svg" alt="Measured on agentmods" 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.00061 | $0.00595 |
| Opus 5 | $0.00030 | $0.00298 |
| Sonnet 5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
marketing-content-linkedin-post 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Post Generation
Draft pipeline for a content idea of type linkedin_post.
When to Use
- Idea with
content_type: linkedin_post - User wants LinkedIn-native copy (not cross-posted blog summary)
Prerequisites
- Content idea file + firm/service/ICP/persona context
- Current agent/LLM session
- Do NOT run Exa reference search (skipped for this type)
Prompt layering
- Base writer (style only)
- Quality layer
- LinkedIn format layer →
references/format-requirements.md
Optional: workspace/firm/content-guidelines/linkedin-post.md
Follow the shared draft gate and writing quality rules in docs/content-generation.md.
Use buyer_question, unique_angle, proof_source, next_action, and
research_mode from the idea; do not write from title + description only.
Output format (critical)
- Plain text — NOT Markdown headers
- One sentence per line
- 150–250 words optimal; max ~300 words / 3000 chars
- 0–2 emojis if brand-appropriate
- 2–3 hashtags at end
- Engagement question at end
- No bullet lists (hurts engagement)
- First-person voice (I, we, you)
Stage → framework (from format prompt)
| Stage | Framework |
|---|---|
| Problem | Story Hook, Poll |
| Concept | Category, This-vs-That |
| Education | Framework, How-To |
| Decision | Comparison, Data |
| Vendor | CSR, Behind-the-Scenes |
Output path
Brand scope. In a multi-brand workspace the draft inherits the idea file's brand: write to workspace/marketing/content/{brand}/drafts/… — same brand segment as the idea. See the Brand Scope Gate in AGENTS.md.
workspace/marketing/content/drafts/linkedin/{slug}.md
Frontmatter: idea, content_type, buying_stage, service, icp, persona,
generated_at. Body = plain text only. Title in frontmatter for filing.
Run scripts/validate-content-draft.sh {output}. Update idea frontmatter to
status: generated after the draft validates.
Related Skills
marketing-content-x-post — different length/platform rules
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 76 lines · 61 tokens per session scan A 10d0942653fd
marketing-content-linkedin-post is a skill published in the GitHub repository b2bforce/b2bforce (2 stars, last pushed 18d ago), licensed MIT. It adds 61 tokens to every session and 595 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-31.
Other skills, from other repositories
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.
tracking-plan
Master analytics tracking plan for PLG and B2B SaaS — unified event taxonomy, pixel strategy (1P and 3P tagging), marketing attribution architecture, CDP implementation (Segment, Rudderstack), product analytics (Amplitude, Mixpanel, PostHog), CRM tracking (HubSpot, Salesforce), and analytics infrastructure design. Use…