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 ericrisco/rsc-harness --skill linkedin-strategygit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/linkedin-strategy)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/linkedin-strategy"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/linkedin-strategy/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/ericrisco/rsc-harness/linkedin-strategy"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/linkedin-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00126 | $0.03179 |
| Opus 5 | $0.00063 | $0.01589 |
| Sonnet 5 | $0.00025 | $0.00636 |
| Haiku 4.5 | $0.00013 | $0.00318 |
Grade A, and why
linkedin-strategy 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Strategy — The Presence as a System, Not the Next Post
You operate at account/presence altitude. You decide the territory (what this presence is known for, who it is for) and the system (pillars, cadence, where content lives, the social-selling rhythm) over months. You never write the post, build the carousel, run the DMs, or hit the API — those are single-asset jobs you route out. Mixing altitudes is the #1 reason LinkedIn advice goes generic: an account-level question answered with a tactic about one post produces noise and regresses to blog-post defaults.
Your spine is a read/write loop with the presence's own history. You read the accumulated learnings before deciding and write the decision back, so the next session compounds instead of restarting from a generic "post 3 times a week" template.
Altitude boundary — route single-asset work out
| The ask | Skill | Why it is not you |
|---|---|---|
| Post copy, hook, body for one update | ../linkedin-content/SKILL.md |
You set the pillar and POV; content writes inside it. |
| A carousel / document-post deck | ../linkedin-carousels/SKILL.md |
A single asset's format craft, not the system. |
| Connection requests, DMs, sequences | ../linkedin-outreach/SKILL.md |
You set the social-selling rhythm; outreach runs the individual threads. |
| Raw analytics, OAuth, rate limits | ../linkedin-api/SKILL.md |
You consume the numbers; the API fetches them. |
| Cross-platform calendar / scheduling | ../content-engine/SKILL.md, ../social-publisher/SKILL.md |
Multi-platform planning/posting, not LinkedIn presence architecture. |
| Abstract tone/voice rules | ../brand-voice/SKILL.md |
Voice in the abstract; you decide positioning and pillars. |
You are the only LinkedIn skill that operates at account altitude and persists its decisions to the wiki. Every sibling works on a single asset or a single thread.
1. Read the wiki FIRST — before any decision
Read 02-DOCS/wiki/linkedin/ before you decide anything. Why: a positioning or cadence call made without the account's own dwell-time and SSI history is just generic advice with a name on it. The whole value of this skill is that decisions compound.
What ships with it
5 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.
- 8d ago First seen · 180 lines · 126 tokens per session scan A 4a651967196a
linkedin-strategy is a skill published in the GitHub repository ericrisco/rsc-harness (81 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 3,179 once invoked, about $0.0006 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
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
setting-up-a-project
Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the brainstorming…
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
requirements-elicitation
Turns vague intent into testable requirements.
dispatching-parallel-agents
Runs independent subtasks concurrently via sub-agents.