linkedin-comment-reply-manager

linkedin-comment-reply-manager is a skill for Claude Code from TaplioOfficial/taplio-linkedin-plugin. It costs 131 tokens per session (2,334 once invoked), scanned A, a copy of linkedin-comment-reply-manager, MIT.

A LinkedIn comment assistant that finds unanswered comments under your posts, sorts them by type, and drafts replies in your voice. You approve the replies before they are scheduled.

In plain words
What is it for?
It is for clearing the comment inbox on your LinkedIn posts and preparing replies. It can handle questions, pushback, lead signals, praise, and spam as separate cases.
Why use it?
It removes the need to manually search through comments and decide how to respond to each one. It also separates questions, disagreement, potential leads, praise, and spam.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the taplio plugin — 26 skills shipped together

Good fit It is for clearing the comment inbox on your LinkedIn posts and preparing replies. It can handle questions, pushback, lead signals, praise, and spam as separate cases.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/taplioofficial/taplio-linkedin-plugin/linkedin-comment-reply-manager
Install

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.

Any agent
npx skills add TaplioOfficial/taplio-linkedin-plugin --skill linkedin-comment-reply-manager
Clone the repo
git clone --depth 1 https://github.com/TaplioOfficial/taplio-linkedin-plugin

Made for: Claude Code.

Or install taplio, the plugin that ships this one along with the rest of its 26 skills.

Wrote 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.

agentmods badge for linkedin-comment-reply-manager

README.md
[![agentmods](https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-plugin/linkedin-comment-reply-manager/github.svg)](https://agentmods.dev/skills/taplioofficial/taplio-linkedin-plugin/linkedin-comment-reply-manager)
Your own site
<a href="https://agentmods.dev/skills/taplioofficial/taplio-linkedin-plugin/linkedin-comment-reply-manager"><img src="https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-plugin/linkedin-comment-reply-manager/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.

agentmods 80×15 button for linkedin-comment-reply-manager

Your own site · 80×15
<a href="https://agentmods.dev/skills/taplioofficial/taplio-linkedin-plugin/linkedin-comment-reply-manager"><img src="https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-plugin/linkedin-comment-reply-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 131 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00131 $0.02334
Opus 5.5 $0.00052 $0.00934
Sonnet 5.5 $0.00026 $0.00467
Haiku 4.5 $0.00013 $0.00233

Measured 23d ago against content hash 9504df6a1dae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

linkedin-comment-reply-manager 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 23d 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.

Origin

This is a copy

95% identical to linkedin-comment-reply-manager — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/linkedin-comment-reply-manager/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LinkedIn Comment Reply Manager

The first hour after a post is where reach is won, and the author's replies are what keep the thread alive. This skill finds every comment still waiting under the user's posts and answers them in their voice.

When to trigger

The user says "reply to my comments", "what is waiting under my posts", "answer the comments on my last post", "clear my LinkedIn inbox", "keep my thread going", or runs the Daily Engagement Routine.

Inputs to ask for (only if missing)

  1. Which posts : default to the posts published in the last 7 days that have comments. The user can name one post, a window, or "everything".
  2. Tone guardrails, if any (formal, playful, never mention pricing). Voice and language come from get_me.
  3. Whether to approve replies one by one or as a batch. Default : one batch review, one go.

The 5 buckets

Triage every comment into one bucket, in this priority order :

  1. Question : they ask something. Answer it specifically. Highest value, highest reach.
  2. Pushback : they disagree or challenge. Answer with respect and one concrete point. These threads travel furthest.
  3. Lead signal : the commenter matches the user's target audience, asks about their method, offer, or results, or shares their own situation. Answer, then flag them for the Warm Lead Finder skill.
  4. Praise or agreement : short, warm, specific. Add a follow-up question to extend the thread when the commenter looks worth talking to.
  5. Spam or bait : self-promotion, generic AI filler, "DM me", trolling. Do not reply. List them so the user knows they were seen.

Process

  1. Orient : identity, username, language, target audience.
  2. List the user's recent posts and keep the ones with comments, newest first. Posts under 48 hours old come first.
  3. Pull the comments still waiting under those posts, a handful of posts at a time.
  4. Triage each comment into a bucket. Note pinned comments and comments with replies already under them (reply_count) : those threads are visible to more people.
  5. Draft one reply per comment in buckets 1 to 4 : 1 to 3 sentences, specific to what they wrote, first name when natural, a question at the end when the thread deserves to continue.
  6. Present everything in one review table. The user approves all, edits some, or drops some.
  7. Save each approved reply as a Taplio comment draft targeting that comment, then, on one explicit go for the batch, commit them. Quote the scheduled time of each.
  8. Close with the queue status and the lead signals to pass on.

Read the full file on GitHub · 111 lines

Changes

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.

  1. 23d ago Changed · +2 lines 9504df6a1dae
  2. 25d ago First seen · 109 lines · 131 tokens per session scan A 692b89829d2d

Subscribe to this mod's changes

linkedin-comment-reply-manager is a skill published in the GitHub repository TaplioOfficial/taplio-linkedin-plugin (3 stars, last pushed 7d ago), licensed MIT. It adds 131 tokens to every session and 2,334 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to linkedin-comment-reply-manager, differing in 0 lines, and is treated as a copy.

Related

linkedin-comment-reply-manager compared with skills from other repositories

linkedin-comment-reply-manager next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
linkedin-comment-reply-managerTaplioOfficial/taplio-linkedin-pluginSkill37d agoMITA131Claude Code
chief-strategy-officercbrock84/headcountSkill2.6k19d agoMITA93Claude Code
ai-ml-governancecbrock84/headcountSkill2.6k19d agoMITA83Claude Code
paid-advertisingcbrock84/headcountSkill2.6k19d agoMITA78Claude Code
customer-onboarding-and-implementationcbrock84/headcountSkill2.6k19d agoMITA94Claude Code
financial-statement-analysiscbrock84/headcountSkill2.6k19d agoMITA93Claude Code
events-and-field-marketingcbrock84/headcountSkill2.6k19d agoMITA65Claude Code