Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Casper-Studios/casper-marketplace/plugin install content-marketingWrote 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/casper-studios/casper-marketplace/linkedin-post-generator)<a href="https://agentmods.dev/skills/casper-studios/casper-marketplace/linkedin-post-generator"><img src="https://agentmods.dev/badge/skills/casper-studios/casper-marketplace/linkedin-post-generator/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/casper-studios/casper-marketplace/linkedin-post-generator"><img src="https://agentmods.dev/badge/skills/casper-studios/casper-marketplace/linkedin-post-generator.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.00097 | $0.02311 |
| Opus 5 | $0.00048 | $0.01156 |
| Sonnet 5 | $0.00019 | $0.00462 |
| Haiku 4.5 | $0.00010 | $0.00231 |
Grade A, and why
linkedin-post-generator 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 9d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Post Generator
Generate LinkedIn posts from shared source material, written in each user's personal style.
How It Works
- Personal style profile — stored locally at
~/.config/casper/linkedin-style.md(never committed) - Source config — stored locally at
~/.config/casper/linkedin-sources.md(never committed) - Shared source material — meeting transcripts, Slack dumps, docs in
source-material/ - Prompt template — extraction rules, voice guidelines, few-shot examples in
references/prompt-template.md
First Run: Style Setup
Check if ~/.config/casper/linkedin-style.md exists.
If it does NOT exist, run the style setup flow:
- Say: "Welcome to the LinkedIn Post Generator! Before we start, I need to understand your writing style."
- Say: "Share 3 LinkedIn posts that match the style you want. You can either paste the post links (e.g.
https://linkedin.com/posts/...) or paste the text directly." - Wait for the user to provide 3 posts
- If the user provides LinkedIn URLs, fetch the post content using the
apify-scrapersskill from theresearchplugin:
If the script isn't found (thepython ${CLAUDE_PLUGIN_ROOT}/../../bizdev/research/skills/apify-scrapers/scripts/scrape_linkedin_posts.py search "{url}" --max-posts 1researchplugin isn't installed) or the call fails, tell the user: "LinkedIn URL fetching needs theresearchplugin (/plugin install research) — paste the post text instead for now." Then continue with pasted text. - Analyze the posts for: tone, sentence length, vocabulary, formatting habits, hook style, CTA style, use of questions, paragraph length, overall energy
- Create
~/.config/casper/directory if it doesn't exist - Save the analysis to
~/.config/casper/linkedin-style.mdusing this format:
# LinkedIn Style Profile
Generated: [date]
## Tone
[analysis]
## Structure Patterns
[paragraph length, line breaks, formatting habits]
## Hook Style
[how they open posts]
## CTA / Closing Style
[how they end posts — questions, challenges, etc.]
## Vocabulary & Phrases
[distinctive phrases, word choices, energy level]
## Sample Posts
[the 3 original posts, for reference]
What ships with it
4 files 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.
- 9d ago First seen · 166 lines · 97 tokens per session scan A 5cee48f95d1d
linkedin-post-generator is a skill published in the GitHub repository Casper-Studios/casper-marketplace (12 stars, last pushed 4d ago), licensed MPL-2.0. It adds 97 tokens to every session and 2,311 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…