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/practicalswan/agent-skills/linkedin-create-postnpx skills add PracticalSwan/agent-skills --skill linkedin-create-postgit clone --depth 1 https://github.com/PracticalSwan/agent-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/practicalswan/agent-skills/linkedin-create-post)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/linkedin-create-post"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/linkedin-create-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 | $0.00047 | $0.02278 |
| Opus 5 | $0.00023 | $0.01139 |
| Sonnet 5 | $0.00009 | $0.00456 |
| Haiku 4.5 | $0.00005 | $0.00228 |
Grade A, and why
linkedin-create-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 yesterday.
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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a LinkedIn post
Use the user's existing Chrome session to prepare and publish a LinkedIn post without requesting account credentials or inspecting browser storage. Keep the writing specific to the user's work and verify the result on LinkedIn after publication.
Route the request
- Confirm that the user wants a LinkedIn post created, edited, or published.
- Select the browser route from the active host capabilities below. Do not infer browser control from the model provider or from a generic web-search tool.
- Prefer a LinkedIn connector only when the user did not explicitly request Chrome and the connector supports the exact publishing action.
- If no authenticated browser or write-capable connector is available, prepare the final copy and media plan, then stop at a clear handoff. Never claim that a post was published.
Browser host routing
- Codex: Use the current
chrome:control-chromeor equivalent host-exposed Chrome workflow when available. Read that workflow before interacting with the browser, and preserve its tab, upload, confirmation, and recovery rules. - Claude Code with direct Anthropic access: Native Claude in Chrome is an
option only when the account meets Anthropic's current paid-plan,
authentication, browser-extension, and
/chromeprerequisites. Verify the integration is actually available before using it. - Claude Code with a third-party endpoint, including the GLM Coding Plan: Do not assume native Claude in Chrome is available. Inspect the active Claude Code MCP configuration and health first. Use a connected, user-approved browser automation MCP such as Chrome DevTools, Puppeteer, or Playwright only through the tool names that the current session exposes.
- Claude Code
WebFetch, web search, and provider-specific search or reader tools are not authenticated browser controls and cannot publish a LinkedIn post. - If the selected browser route cannot reuse the user's authenticated profile, stop for user sign-in or give a manual handoff. Never request cookies, passwords, session tokens, or two-factor codes.
What ships with it
2 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.
- yesterday First seen · 217 lines · 47 tokens per session scan A 6eec7f7cb4c9
linkedin-create-post is a skill published in the GitHub repository PracticalSwan/agent-skills (13 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 2,278 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-09-03.
Other skills, from other repositories
LinkedIn automation via the Linked API CLI - fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and run Sales Navigator and custom workflows. Use when the user wants to interact with LinkedIn.
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
cookie-debugging
Uses Chrome DevTools MCP for inspecting, debugging, and testing cookies, session state, authentication issues, and cookie consent compliance. Use when diagnosing 401/403 errors, authentication redirects, session expiration, Cookie/Set-Cookie header issues, cookie banner consent conformance, or third-party…
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…