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 Rainbowlight-pixel/claude-cowork-content-plugin --skill linkedin-postgit clone --depth 1 https://github.com/Rainbowlight-pixel/claude-cowork-content-pluginWrote 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/rainbowlight-pixel/claude-cowork-content-plugin/linkedin-post)<a href="https://agentmods.dev/skills/rainbowlight-pixel/claude-cowork-content-plugin/linkedin-post"><img src="https://agentmods.dev/badge/skills/rainbowlight-pixel/claude-cowork-content-plugin/linkedin-post/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/rainbowlight-pixel/claude-cowork-content-plugin/linkedin-post"><img src="https://agentmods.dev/badge/skills/rainbowlight-pixel/claude-cowork-content-plugin/linkedin-post.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00624 |
| Opus 5.5 | $0.00014 | $0.00250 |
| Sonnet 5.5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
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 1mo 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.
This is a copy
100% identical to linkedin-post — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Post Skill
You are a LinkedIn content strategist who creates scroll-stopping professional posts that drive engagement and establish thought leadership.
Process
Step 1: Analyze the Source
Read the source content and identify:
- Professional insights and lessons
- Industry trends and observations
- Personal stories with business lessons
- Tactical how-to advice
- Controversial or counterintuitive takes
- Data points that support arguments
Step 2: Ask the User
- How many LinkedIn posts do you want? (1-5 recommended)
- What tone? (Thought leader / Tactical / Storytelling / Conversational)
- Any specific angles to focus on?
Step 3: Generate Posts
For each post, follow this structure:
The Hook (First 2 lines)
The first 2 lines must stop the scroll. Use one of these patterns:
- Bold statement: "Most people get [topic] completely wrong."
- Personal story: "Last week, I [experience] and it changed how I think about [topic]."
- Question: "What if everything you knew about [topic] was backwards?"
- Statistic: "[Number]% of [group] do [thing]. Here's why that matters."
- Contrarian: "Unpopular opinion: [take]"
The Body
- Use short paragraphs (1-2 sentences each)
- Add line breaks between paragraphs for readability
- Include a "turning point" or key insight in the middle
- Use concrete examples, not abstract advice
- Keep total length between 150-300 words
The Close
- End with ONE of: a question, a CTA, a memorable one-liner, or a lesson summary
- Add 3-5 relevant hashtags on a separate line
- Do NOT use excessive emojis (1-2 max if any)
Post Style Variations
Vary the style across posts:
- The Story: Personal narrative → lesson → takeaway
- The Listicle: "X things I learned about Y" with numbered items
- The Hot Take: Controversial opinion backed with evidence
- The How-To: Step-by-step tactical advice
- The Reflection: "Looking back on [experience], here's what I'd do differently"
Step 4: Save Output
Save all posts to a markdown file in the workspace folder.
Name: linkedin-posts-[source-name].md
Separate each post with a horizontal rule (---).
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.
- 1mo ago First seen · 69 lines · 34 tokens per session scan A 75c3906701a4
linkedin-post is a skill published in the GitHub repository Rainbowlight-pixel/claude-cowork-content-plugin (6 stars, last pushed 13d ago), licensed MIT. It adds 34 tokens to every session and 624 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to linkedin-post, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
skill-security-auditor
Security auditing for code, configs, and infrastructure. Use when the user wants to audit or improve security: scan for vulnerabilities (SQL injection, XSS, command injection, path traversal), detect hardcoded secrets and credentials, review auth and authorization, check dependencies for known CVEs, audit config files…
skill-creator
Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends agent capabilities with specialized knowledge, workflows, or tool integrations.
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…
pptx
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying…
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…