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 noahlz/claude-plugins --skill craft-linkedin-postgit clone --depth 1 https://github.com/noahlz/claude-pluginsWrote 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/noahlz/claude-plugins/craft-linkedin-post)<a href="https://agentmods.dev/skills/noahlz/claude-plugins/craft-linkedin-post"><img src="https://agentmods.dev/badge/skills/noahlz/claude-plugins/craft-linkedin-post.svg" alt="Measured on agentmods" 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.00019 | $0.00559 |
| Opus 5 | $0.00010 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
craft-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 8d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow
- Ask what the user wants to write about — angle, audience, examples. Do NOT draft yet.
- Draft the post. Output in full.
- Dispatch the
linkedin-revieweragent to review the draft. Output the feedback. Ask direction. Do NOT revise yet. - Revise passage-by-passage — original and revised side by side, pause after each; do not continue until approved:
| Response | Action |
|---|---|
| "original" | Keep as-is |
| "revised" | Use your version |
| "mix" / tweaks | Combine elements |
| Direct wording | Use verbatim |
- Assemble the final post and output it in full.
- Optionally re-run
linkedin-reviewerfor final review. Output findings; let the user decide.
Voice
- Story first, conclusion second. Open with a specific experience, draw the takeaway from it.
- Conversational. Rhetorical questions, parenthetical asides, sentence fragments. Not presenting — talking.
- Self-deprecating. Admit mistakes and false starts ("I went down that road.").
- Opinionated. State positions directly. No "in my experience" hedging.
- Humor via asides. Wry parentheticals (e.g., "stop it with the em-dashes, Claude!"). Never forced.
- Low-key closer. Question or casual sign-off — never a call to action.
- No buzzwords. No "leverage," "game-changer," "unlock," "dive deep." No listicle structure.
- Concrete. Name the tool, quote the error, show the config line.
LinkedIn Constraints
| Rule | Detail |
|---|---|
| No markdown | LinkedIn doesn't render bold, italics, or headers |
| No linked text | Raw URLs only |
| Short paragraphs | Readers skim on mobile |
| Plain bullets | Use •, -, or line breaks — not markdown lists |
Editorial Rules
- Preserve voice. Don't normalize to generic "LinkedIn voice."
- No overhauls. Rewriting >30% of a passage means you've gone too far.
- Verbatim wording. When the user dictates exact words, use them.
- One passage at a time. Never batch approvals.
- Keep self-deprecating humor unless the user removes it.
- Don't soften opinions. Flag harsh lines — never silently tone them down.
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.
- 8d ago First seen · 52 lines · 19 tokens per session scan A 3cd65c847bc2
craft-linkedin-post is a skill published in the GitHub repository noahlz/claude-plugins (5 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 559 once invoked, about $0.0001 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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…