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/styfinity/linkedin-engine/linkedin-story-minernpx skills add styfinity/linkedin-engine --skill linkedin-story-minergit clone --depth 1 https://github.com/styfinity/linkedin-engineWrote 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/styfinity/linkedin-engine/linkedin-story-miner)<a href="https://agentmods.dev/skills/styfinity/linkedin-engine/linkedin-story-miner"><img src="https://agentmods.dev/badge/skills/styfinity/linkedin-engine/linkedin-story-miner.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.00038 | $0.00524 |
| Opus 5 | $0.00019 | $0.00262 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
linkedin-story-miner 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 5d 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.
What it actually says
LinkedIn Story Miner
Your work is full of posts you haven't written yet. This skill pulls the proof stories out of what you just did, strips the identifying details, and ranks them by how hard they prove you can do the job.
Inputs
- A description of recent work, wins, or builds: $ARGUMENTS
- The brief (persona, offer, the operator's positioning as a Revenue Partner) loads automatically.
Do this
- Read the raw work and pull out every candidate that carries proof. A proof story has one of: a before/after number, a hard-won lesson, or a contrarian result that goes against the obvious play.
- Anonymise each one. Strip names, company names, and any detail that identifies a person or client. Keep the real numbers. "Took a client from X to Y" stays as a number with no name attached.
- Score each story on proof strength: how strongly it shows the operator can produce the outcome the ICP wants. A measured before/after outranks a vague lesson.
- Rank them strongest proof first.
- For each, name the angle (the single point it makes) and suggest the hook formula that fits: the contrarian take, the before/after, the mistake-I-made, the counterintuitive number, or the behind-the-build.
Output
A ranked list of story seeds. For each: the anonymised proof (one or two lines, numbers intact), the angle, and the suggested hook formula. Top seed first. End with a one-line note on which seed to turn into a post next, and a pointer to draft it.
Rules
- Keep numbers, drop names. This is for public posts, so no real person, company, or client is identifiable.
- Never fabricate a result or round a number up. If a story has no real proof, mark it as a softer "lesson" seed, do not invent a metric.
- Attribute every number to "a post", "a client", or "an operator", never a named entity.
- No em-dashes. This is a seed list, not a finished draft. Hand the chosen seed to a drafting skill, then run /linkedin-humanizer before it goes live.
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.
- 5d ago First seen · 30 lines · 38 tokens per session scan A 0b6eca7d814d
linkedin-story-miner is a skill published in the GitHub repository styfinity/linkedin-engine (7 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 524 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-08-31.
Other skills, from other repositories
LinkedIn Automation
Automate LinkedIn marketing, lead generation, content publishing, and professional networking.
lemlist-campaign-from-icp
Use when the user says "create a lemlist campaign for X", "build a lemlist campaign from this ICP", "spin a lemlist campaign for Y", "ICP to lemlist", "natural language to lemlist campaign", "draft a lemlist campaign", "lemlist campaign for VPs/Managers/ICs at Z", or any variant indicating they want to turn a…
copywriting-ic-sequence
Writes a 3-email outbound sequence targeting Individual Contributors (SDR, AE, BDR, Account Manager, Marketing Specialist, Sales Rep, RevOps Analyst, CS Rep, etc.). Use this skill whenever the user wants to write cold emails for an IC, says "write me a sequence for SDRs", "draft emails targeting AEs", "emails for…
gtm-action-thinker
Brainstorms, challenges, and pushes any GTM idea to its fullest potential — on both the idea itself and its execution. Use this skill whenever the user shares a campaign idea, an outbound angle, a workflow concept, a positioning hypothesis, or any GTM initiative and wants to think it through deeply. Even if they just…
lost-deal-revival-agent
Drafts revival messages for closed-lost deals when a public company signal contradicts the original objection. Receives the signal-pair watcher's fire payload, fetches the verbatim Claap objection quote, and produces a 2-line draft that quotes it back. Default output is a HubSpot task for human review. Optional…
provider-builder
Use when a teammate wants to add a new vendor to YALC for an existing capability without shipping a release. Triggers include "add a new provider for X", "wire up [vendor] to YALC", "build an adapter for [vendor]", "I want to use [vendor] for [capability]", "add Apollo for icp-company-search", or any variant…