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 styfinity/linkedin-engine --skill linkedin-comment-enginegit 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-comment-engine)<a href="https://agentmods.dev/skills/styfinity/linkedin-engine/linkedin-comment-engine"><img src="https://agentmods.dev/badge/skills/styfinity/linkedin-engine/linkedin-comment-engine/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/styfinity/linkedin-engine/linkedin-comment-engine"><img src="https://agentmods.dev/badge/skills/styfinity/linkedin-engine/linkedin-comment-engine.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.00039 | $0.00522 |
| Opus 5.5 | $0.00016 | $0.00209 |
| Sonnet 5.5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
linkedin-comment-engine 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.
What it actually says
LinkedIn Comment Engine
Warming starts in the comments, not the inbox. This skill writes comments that add real value to someone else's post and quietly pull profile views from the people watching.
Inputs
- The post you want to comment on (paste the full text) and the author's relevance to your ICP (a buyer, a peer, a connector, an audience overlap): $ARGUMENTS
- The brief (persona tone, pains, offer, voice) loads automatically.
Do this
Write two comment variants the user can pick from:
- Add ONE genuine thing. Either a specific insight, a build detail, or a number from real work (attribute to "a post" or "a client", never a named entity). Not "great post", not generic praise.
- Agree-then-extend, or respectfully reframe. Build on the author's point with a second-order observation, or offer a sharper angle without making them wrong.
- Leave a soft hook at the end that earns a profile click: a half-told result, a "here is what most miss", or a question that signals you operate in their world. No pitch, no link.
- Variant A is short and punchy (one or two lines). Variant B is a longer mini-teaching comment (three to five lines) that demonstrates competence.
Output
Two labelled comment variants (A short, B mini-teaching) plus a one-line note on which to use when: A for high-traffic posts where brevity wins attention, B when the author is a direct ICP and you want them to read your whole profile.
Rules
- Never pitch in a comment. Never argue to win. The job is to make a decision-maker click your profile, not to score a point.
- Add value the author would thank you for, even if they never reply.
- Anonymise all proof: keep the numbers, drop the names.
- No em-dashes, no exclamation marks, no "great post", no "thanks for sharing".
- Draft only. Claude drafts, the operator reads and posts. When a reply comes back warm, hand it to /linkedin-reply-triager. Run /linkedin-humanizer on either variant if it reads stiff.
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 · 31 lines · 39 tokens per session scan A 097e37e926f6
linkedin-comment-engine is a skill published in the GitHub repository styfinity/linkedin-engine (9 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 522 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
LinkedIn Automation
Automate LinkedIn marketing, lead generation, content publishing, and professional networking.
linkedin-carousels
Use when building a LinkedIn carousel / document post — the swipeable multi-page PDF — slide by slide: cover hook, narrative arc, one idea per slide, CTA closer, PDF export spec. NOT the account/format plan (that is linkedin-strategy), NOT a text or single-image feed post (that is linkedin-content), NOT a 16:9 talk…
deepline-ads-audiences
Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal…
deepline-analytics
Use this skill when answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline. Triggers on phrases like 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', or any use of…
deepline-engine
Build, publish, and verify a Deepline Play as a durable state machine over Customer DB tables, including a small paid pilot. Invoke this skill explicitly when the user asks to build an engine.
deepline-gtm
GTM leads, enrichment, outreach, Plays, developer signals/Reo.dev. Providers…