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 aakashg/pm-claude-skills --skill linkedin-post-writergit clone --depth 1 https://github.com/aakashg/pm-claude-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/aakashg/pm-claude-skills/linkedin-post-writer)<a href="https://agentmods.dev/skills/aakashg/pm-claude-skills/linkedin-post-writer"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-skills/linkedin-post-writer/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/aakashg/pm-claude-skills/linkedin-post-writer"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-skills/linkedin-post-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 56 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00065 | $0.01767 |
| Opus 5 | $0.00032 | $0.00883 |
| Sonnet 5 | $0.00013 | $0.00353 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
linkedin-post-writer 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 12d 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 Writer
Turn a rough idea into one publishable LinkedIn post: one hook, one format, one CTA.
Step 0 — Read first
Read these before writing a single line. Do not write from memory of "how LinkedIn posts go."
| Source | Path | What to extract |
|---|---|---|
| Project context | CLAUDE.md |
Who the user is, their product, banned words, audience |
| Post patterns | references/post-patterns.md |
5 full worked posts + why each works |
| User's raw input | whatever they pasted | The one insight, the specific numbers, the personal detail |
| Prior posts | any file/link the user names | Their actual voice — match it, do not invent one |
If references/post-patterns.md is missing, say so and proceed with the worked example below only.
Constraints
These are mandatory. Violating any one means the draft is not done.
- Hook is ONE line. Two-line hooks lose reach. No exceptions.
- Total body 800–1,300 characters. Under 800 reads thin; over 1,300 truncates in feed.
- Exactly ONE call to action. Not two, not "and follow me."
- Zero or one emoji. Zero is the default.
- No paragraph longer than 3 lines.
- The post must contain at least one specific number, name, or timeframe.
- Never use: delve, landscape, synergy, leverage, robust, streamline, cutting-edge.
- Never open with "I'm excited to announce" or "Thrilled to share."
- No hashtags in the body. If requested, 3–5 after a line break at the end.
- Lead with the insight, never the product. Product appears in context or not at all.
Existence check
Before drafting, verify three things:
- The insight — one sentence the reader did not already know.
- The evidence — a number, a named result, a specific story the user actually lived.
- The audience — a specific person or role, not "professionals."
If two of three are missing, do not draft. Say which are missing and ask for exactly those. A post with no insight and no evidence is engagement bait, and publishing it costs the user credibility.
What ships with it
1 file 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.
- 12d ago First seen · 166 lines · 65 tokens per session scan A 310eff42a2b7
linkedin-post-writer is a skill published in the GitHub repository aakashg/pm-claude-skills (106 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,767 once invoked, about $0.0003 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
utility-pm-skill-builder
Guides contributors from a PM skill idea to a complete Skill Implementation Packet aligned with pm-skills conventions. Runs gap analysis, validates through a Why Gate, classifies by type and phase, generates draft files, and writes to a staging area for review before promotion.
utility-update-pm-skills
Validates internet access, compares the locally installed pm-skills version against the latest public release, and updates local files with conflict-aware overwrite-or-skip options. Produces an update report listing changed files, skipped files, and new capabilities. Use when you want to bring a local pm-skills…
discover-journey-map
Maps a customer journey across stages, touchpoints, emotional curve, pain points, and moments of truth into a markdown artifact with an optional mermaid timeline or flowchart. Use when synthesizing existing research into the shape of a customer's experience, end-to-end or for one phase. Without research signal yet…
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
utility-pm-skill-validate
Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.
tool-foundation-sprint-founding-hypothesis
Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe, what-could-prove-us-wrong, and recommended next validation step. Use after Magic Lenses is signed. Strict canonical…