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 matellez/claude-skills --skill linkedin-postgit clone --depth 1 https://github.com/matellez/claude-skillsWrote 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/matellez/claude-skills/linkedin-post)<a href="https://agentmods.dev/skills/matellez/claude-skills/linkedin-post"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/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/matellez/claude-skills/linkedin-post"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/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.00137 | $0.01425 |
| Opus 5.5 | $0.00055 | $0.00570 |
| Sonnet 5.5 | $0.00027 | $0.00285 |
| Haiku 4.5 | $0.00014 | $0.00143 |
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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Post Skill
This skill runs automatically when the user wants a LinkedIn post. Apply all rules below before delivering output. Do not explain what you are doing. Just deliver the post.
HOW TO SET UP THIS SKILL
Replace the [PLACEHOLDER] sections with your own profile before adding this file to your Claude Project.
Your Profile
Name: [Your full name]
Role and background: [1-2 sentences. Your title, domain, years of experience, and current focus. Example: "B2B SaaS marketing leader, 15 years in demand generation and RevOps. Currently consulting and writing about pipeline strategy and AI-assisted marketing."]
Content focus areas: [List 4-6 topics you post about regularly. Example:
- Original takes on B2B demand gen and pipeline strategy
- AI tools and productivity for marketers and operators
- Commentary on industry articles or trends
- Lessons from building GTM functions at B2B SaaS companies]
Audience: [Describe who reads your content. Example: "B2B marketers, RevOps leaders, demand gen practitioners, founders, and recruiters in the SaaS and tech space."]
Voice Rules (Non-Negotiable)
These apply to every post, no exceptions.
- Short and punchy. Most sentences under 12 words. Cut anything that does not add meaning.
- Lead with the sharpest idea. Do not build up to the point. Start with it.
- Active voice only. Never passive.
- No em dashes. Use a period or comma instead.
- No "agree or disagree?" endings. This is the most common LinkedIn cliche. Never use it.
- No fluff openers. Never start with "In today's landscape," "As a [title]," "I've been thinking a lot about," or any variation.
- No sycophantic language. No "excited to share," "humbled to announce," "honored to."
- No AI vocabulary words. No: delve, foster, crucial, pivotal, landscape, tapestry, underscore, showcase, testament, vibrant.
- Opinions are required. Neutral posts get ignored. Take a position.
- Outcome framing when relevant. Connect ideas to business results, not just activities.
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 · 201 lines · 137 tokens per session scan A 5d22ae008b7b
linkedin-post is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 6mo ago), licensed MIT. It adds 137 tokens to every session and 1,425 once invoked, about $0.0005 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-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.
rudder-instrumentation-debugging
Diagnoses and fixes validation errors, schema issues, and instrumentation problems. Use when debugging validation errors, schema issues, or instrumentation problems.
rudder-ai-events-verify
Verifies RudderStack AI events locally: captures what an instrumented app or MCP server sends, validates it against the AI events v0.3 schema, and checks joins, counts, identity and content. Use when testing AI events, or when AI or MCP events look wrong or missing.
helius
Skill "helius" from helius-labs/core-ai, covering helius — build on solana, prerequisites, 1. helius mcp server, 2. mcp router surface and 3. api key.