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 cdeistopened/skill-stack --skill x-linkedin-content-relaygit clone --depth 1 https://github.com/cdeistopened/skill-stackWrote 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/cdeistopened/skill-stack/x-linkedin-content-relay)<a href="https://agentmods.dev/skills/cdeistopened/skill-stack/x-linkedin-content-relay"><img src="https://agentmods.dev/badge/skills/cdeistopened/skill-stack/x-linkedin-content-relay/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/cdeistopened/skill-stack/x-linkedin-content-relay"><img src="https://agentmods.dev/badge/skills/cdeistopened/skill-stack/x-linkedin-content-relay.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.00110 | $0.01127 |
| Opus 5.5 | $0.00044 | $0.00451 |
| Sonnet 5.5 | $0.00022 | $0.00225 |
| Haiku 4.5 | $0.00011 | $0.00113 |
Grade A, and why
x-linkedin-content-relay 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X → LinkedIn Content Relay
Something that goes viral on X takes roughly two weeks to reach the LinkedIn audience. That lag is a feature, not a bug. A well-performing X post can be reframed and relayed to LinkedIn ~14 days later to the same audience that hasn't seen it yet — and LinkedIn's audience prefers a different register of voice than X's.
When invoking: Ask for the winning X post (or the content the user wants to reuse), the date it was posted, the LinkedIn audience the user is targeting, and whether the target is tech or non-tech. Then produce the LinkedIn version.
When the relay wins
- Non-tech ICP. Event marketers, HR, healthcare ops, education, manufacturing, services. These audiences live on LinkedIn. X is a trickle. LinkedIn is where the work gets found.
- Delayed-audience fit. Your X post went viral with devs, but the real buyers are PMs and ops leaders who live on LinkedIn. Wait two weeks, relay, capture the second wave.
- Authority posts. Case studies, lessons, numbers. LinkedIn rewards "I learned this" and "here's our number" more than X.
When NOT to relay
- Pure X-native formats: shitposts, memes, crypto-style banter, contrarian one-liners, cold screenshots with no setup.
- Posts whose viral value was the reply chain, not the post itself.
- Posts under 48 hours old — let X do its full cycle first.
The reframing rules
X and LinkedIn are different rooms. Don't copy-paste.
| Axis | X | |
|---|---|---|
| Voice | Punchy, lowercase, ironic OK | Declarative, first-letter caps, earnest |
| Length | 80-200 chars for engagement | 1,200-2,000 chars for feed dwell |
| Framing | "Here's a thing" | "Here's what I learned" |
| Proof | Screenshots, GitHub links | Numbers, outcomes, named companies |
| Opener | Claim or contrarian hook | Story hook, first-person setup |
| Closer | Open question or zero close | "What's your take?" or concrete CTA |
| Media | Video / screenshot native | Native image / carousel PDF |
| External links | Penalized, put in reply | Same penalty; first comment instead |
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 · 74 lines · 110 tokens per session scan A 2116d3b03967
x-linkedin-content-relay is a skill published in the GitHub repository cdeistopened/skill-stack (30 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 1,127 once invoked, about $0.0004 per session on Opus 5.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
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.