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/styfinity/linkedin-engine/linkedin-carousel-writernpx skills add styfinity/linkedin-engine --skill linkedin-carousel-writergit clone --depth 1 https://github.com/styfinity/linkedin-engineWhat 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.00054 | $0.00470 |
| Opus 5 | $0.00027 | $0.00235 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
linkedin-carousel-writer 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.
What it actually says
LinkedIn Carousel Writer
Saveable infographics are the most-saved content type, and saves make a post travel. This skill rewrites a post as carousel slides that mirror it beat for beat, so the carousel and the post reinforce each other.
Inputs
- The post, or the topic to build from: $ARGUMENTS
- The brief (persona, voice profile, offer, pains) loads automatically. If you were handed a topic and no post, write the post beats first, then map slides to them.
Do this
- Read the post and find its beats: the hook, each supporting idea, the close. The slide order maps to this order 1:1.
- Cover slide. Take the hook, big and bold. It must read as a thumbnail and stop the scroll on its own.
- Body slides, 6 to 9 of them. One idea per slide, plus a single line of caption. Each body slide maps to one beat of the post.
- CTA slide. One ask only: comment the keyword, then connect. Keep it short.
- Re-read top to bottom. Cut any slide that carries a second idea or repeats the one before it.
Output
Slide-by-slide copy, labelled Slide 1 to Slide N. Under each slide, a one-line design note: what to emphasise visually (the number, the word, the contrast). End with a one-line pointer: render these as 1080x1350 slides in any carousel tool.
Rules
- One idea per slide. If a slide needs "and", split it.
- Plain words. The cover must work as a thumbnail at small size.
- No em-dashes, no exclamation marks. Short lines, not paragraphs.
- This drafts copy only. The operator approves before anything is rendered or posted.
- Frame any method as Styfinity's own operating principle, never a named outside source.
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 · 31 lines · 54 tokens per session scan A 4f6a55d15362
linkedin-carousel-writer is a skill published in the GitHub repository styfinity/linkedin-engine (7 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 470 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
lemlist-campaign-from-icp
Use when the user says "create a lemlist campaign for X", "build a lemlist campaign from this ICP", "spin a lemlist campaign for Y", "ICP to lemlist", "natural language to lemlist campaign", "draft a lemlist campaign", "lemlist campaign for VPs/Managers/ICs at Z", or any variant indicating they want to turn a…
provider-builder
Use when a teammate wants to add a new vendor to YALC for an existing capability without shipping a release. Triggers include "add a new provider for X", "wire up [vendor] to YALC", "build an adapter for [vendor]", "I want to use [vendor] for [capability]", "add Apollo for icp-company-search", or any variant…
campaign-strategy
Pre-flight strategy advisor for a new campaign. Analyses every past campaign in the local YALC DB (HeyReach campaigns auto-sync on each run), their real outbound copy, where in the sequence each conversation first replied, every prior retro brief, and the validated/proven intelligence file. Then it proposes angle…
copywriting-follow-up
Writes follow-up cold emails after no reply from a prospect. Use this skill whenever the user wants to follow up on an email that got no response, says "write a follow-up", "they didn't reply, what do I send?", "draft a bump email", "write email 2 or 3 of my sequence", or asks how to re-engage a cold prospect. Works…
copywriting-ic-sequence
Writes a 3-email outbound sequence targeting Individual Contributors (SDR, AE, BDR, Account Manager, Marketing Specialist, Sales Rep, RevOps Analyst, CS Rep, etc.). Use this skill whenever the user wants to write cold emails for an IC, says "write me a sequence for SDRs", "draft emails targeting AEs", "emails for…
copywriting-manager-sequence
Writes a 3-email outbound sequence targeting Manager-level buyers (Sales Manager, Marketing Manager, RevOps Manager, Team Lead, Operations Manager, etc.). Use this skill whenever the user wants to write cold emails for a Manager, says "write me a sequence for a Sales Manager", "draft emails targeting managers", or…