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-content-calendarnpx skills add styfinity/linkedin-engine --skill linkedin-content-calendargit 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.00039 | $0.00457 |
| Opus 5 | $0.00019 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
linkedin-content-calendar 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 3d 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 Content Calendar
One week, five posts, five lanes. This skill sets the slate so every post proves a competence the buyer actually pays for, with enough variety that the feed never feels like the same post twice.
Inputs
- The week's theme or the proof on hand, plus which lane needs weight: $ARGUMENTS
- The brief (lanes, voice profile, offer, pains, and what has run recently) loads automatically.
Do this
- Assign one post to each of the five revenue lanes: Get Found, Get Chosen, Get the Meeting, Close the Deal, Operating System.
- Apply the locked variety mix across the five, one type each: a deep operator-playbook post, an ultra-short screenshot-and-share, a second deep post, a proof / business-case post, a punchy mid-length opinion.
- Pick five DIFFERENT hook formulas, one per post. No formula repeats inside the week.
- Check the last six weeks. Do not repeat a framework angle that has run in that window. If the theme forces a repeat, rotate the angle or swap the proof.
- For each post, set the comment keyword (one word, easy to type, tied to the lane's lead magnet or follow-up).
Output
A five-row table with columns: Day, Type, Lane, Hook formula, Angle (one line), Keyword. Then one line naming the through-line that ties the five posts into a single week.
Rules
- Every post must prove a competence the buyer buys. If a post only entertains, cut it and reassign the lane.
- No angle and no hook formula repeated inside the week; no framework angle repeated inside six weeks.
- This skill plans only. It does not write the posts. Hand each row to the drafting skills, then run /linkedin-humanizer on the drafts before anything is scheduled.
- No em-dashes.
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.
- 3d ago First seen · 30 lines · 39 tokens per session scan A eae17a8595ed
linkedin-content-calendar is a skill published in the GitHub repository styfinity/linkedin-engine (7 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 457 once invoked, about $0.0002 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…
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…
copywriting-vp-sequence
Writes a 3-email outbound sequence targeting VP-level buyers (VP Sales, VP Marketing, VP Revenue, VP Operations, VP Product, etc.). Use this skill whenever the user wants to write cold emails for a VP, says "write me a sequence for a VP of Sales", "draft emails targeting VP-level", or provides a VP persona and asks…