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 TaplioOfficial/taplio-linkedin-claude-skills --skill linkedin-swipe-file-buildergit clone --depth 1 https://github.com/TaplioOfficial/taplio-linkedin-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/taplioofficial/taplio-linkedin-claude-skills/linkedin-swipe-file-builder)<a href="https://agentmods.dev/skills/taplioofficial/taplio-linkedin-claude-skills/linkedin-swipe-file-builder"><img src="https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-claude-skills/linkedin-swipe-file-builder/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/taplioofficial/taplio-linkedin-claude-skills/linkedin-swipe-file-builder"><img src="https://agentmods.dev/badge/skills/taplioofficial/taplio-linkedin-claude-skills/linkedin-swipe-file-builder.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.00120 | $0.01866 |
| Opus 5 | $0.00060 | $0.00933 |
| Sonnet 5 | $0.00024 | $0.00373 |
| Haiku 4.5 | $0.00012 | $0.00187 |
Grade A, and why
linkedin-swipe-file-builder 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- linkedin-swipe-file-builder — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Swipe File Builder
A swipe file is a creator's gym. You do not lift the weights, you just look at them. This skill helps the user build their gym.
When to trigger
The user says "how do I build a swipe file", "I save posts but never reuse them", "I want to organize my inspiration", "help me set up a content reference library".
Inputs to ask for
- Where they want to store it (Notion, Airtable, Google Sheet, plain folder, Taplio).
- The niche they create in.
- How many posts they want to start with (10, 25, 50).
The 4-axis classification
Every saved post should be tagged on 4 axes :
- Hook pattern : curiosity, contrarian, number, question, personal stake, before/after, callout.
- Format : story, listicle, opinion, framework, carousel, screenshot, poll, image, video.
- Angle : the specific corner of the niche the post owns (e.g. "pricing for early-stage SaaS", "how to write cold emails for SDRs").
- Why I saved it : the lever that made it stop the user (e.g. "the way they used a number in line 1").
Process
- Set up the storage with these columns : URL, Author, Date saved, Hook pattern, Format, Angle, Why I saved it, My adaptation idea.
- Suggest the user save 1 post per day for 30 days. Quantity beats curation early on.
- Every 2 weeks, review the file and look for clusters : "I keep saving contrarian opinion posts about pricing" = that is the lane to write in.
- Suggest the user write 1 post per week using the structure of one of the saved posts (not the substance).
- Then put the swipe file to work immediately : for every post in the swipe file, write the user a draft of their OWN post that reuses that reference's hook pattern and structure, never its substance, adapted to the user's niche and voice. Present all the drafts and ask the user to validate which ones to keep. Save each approved draft to Taplio (see the MCP section). This turns the reference library into a ready-to-edit content pipeline in one pass.
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 · 105 lines · 120 tokens per session scan A 542a3596b597
linkedin-swipe-file-builder is a skill published in the GitHub repository TaplioOfficial/taplio-linkedin-claude-skills (5 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 1,866 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-08-31.
Other skills, from other repositories
linkedin-humanizer
Remove the AI tells human readers and LinkedIn's AI-slop filter react to in a post or comment: 2026 vocabulary by paragraph density, reveal bridges, staccato fragments, stacked triads, performed sincerity. Tiered rewriter (forensic / strict / aesthetic / all) plus --mode audit pass-fail review and --mode profile voice…
linkedin-marketing
Plan, draft, audit, and publish LinkedIn posts and comments. Use when the user wants to write a viral LinkedIn post, draft a comment or reply on any LinkedIn post URL, audit a draft against 2026 algorithm heuristics, remove AI tells, extract hook formulas from viral posts, or plan a week of content. Powered by the…
linkedin-reply-handler
Draft a reply to a specific existing LinkedIn comment from its URL. Use when the user wants to reply to a comment on any post, or follow up after an author replied to them. Parses the commentUrn, resolves the correct parentComment target (LinkedIn flattens threads to 2 levels), and posts via Publora on approval. Not…
linkedin-post-writer
Draft a new LinkedIn post from scratch using one of 20 2026 hook formulas (anaphora, R.I.P., time-anchor, curiosity-gap, contrarian, controlled A/B, false-binary, and more) plus a founders-edition angle library, picked by engagement goal (comments, reposts, likes, saves). Runs the humanizer pass and schedules via…
linkedin-comment-drafter
Draft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via…
linkedin-content-planner
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post.