linkedin-7-day-warmup

linkedin-7-day-warmup is a skill for Claude Code, Codex from swan-gtm/gtm-skills. It costs 75 tokens per session (613 once invoked), scanned A, original, MIT.

A seven-day activity schedule for warming up a new, inactive, or previously warned LinkedIn account before outreach. It gradually increases normal activity and connection requests.

In plain words
What is it for?
Use it to prepare LinkedIn accounts for campaigns, set daily activity limits, decide when full outreach can begin, and handle warnings safely.
Why use it?
It lowers the chance that a sudden burst of outreach triggers LinkedIn warnings or verification checks. It also gives operators a clear pause-and-resume process when an account is flagged.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare LinkedIn accounts for campaigns, set daily activity limits, decide when full outreach can begin, and handle warnings safely.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swan-gtm/gtm-skills/linkedin-7-day-warmup
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 swan-gtm/gtm-skills --skill linkedin-7-day-warmup
Clone the repo
git clone --depth 1 https://github.com/swan-gtm/gtm-skills

Made for: Claude Code, Codex.

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-7-day-warmup

README.md
[![agentmods](https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/linkedin-7-day-warmup/github.svg)](https://agentmods.dev/skills/swan-gtm/gtm-skills/linkedin-7-day-warmup)
Your own site
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/linkedin-7-day-warmup"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/linkedin-7-day-warmup/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-7-day-warmup

Your own site · 80×15
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/linkedin-7-day-warmup"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/linkedin-7-day-warmup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 613 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00075 $0.00613
Opus 5 $0.00037 $0.00307
Sonnet 5 $0.00015 $0.00123
Haiku 4.5 $0.00007 $0.00061

Measured 9d ago against content hash c05cb8c0c031, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

linkedin-7-day-warmup 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 9d 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.

skills/imad-badreddine/linkedin-7-day-warmup/SKILL.md · 39 lines

How it starts

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

Run this before any new or dormant LinkedIn account sends its first campaign. It produces a seven-day activity schedule and a go/no-go decision for opening full outreach.

The play

  1. Confirm the account's starting state: brand new, dormant, or returning from a warning. A returning account restarts this plan from day 1, never mid-way.
  2. Days 1-2: 3-5 likes and 1 comment per day, up to 5 connection requests per day. Nothing else. The account is being watched hardest here.
  3. Days 3-4: 3-5 likes and 1-2 comments per day, up to 10 connection requests per day.
  4. Days 5-7: start light conversations with accepted connections, up to 15-20 connection requests per day.
  5. After day 7, settle into the steady state: 20 connection requests per day reached gradually, 5-10 likes and 2-3 comments daily, small profile updates weekly. Open full outreach.
  6. Send links only after a prospect has replied, never in a first message.
  7. If the account receives any warning or verification prompt at any point: pause all activity for 48-72 hours, then resume one level below where the warning happened.

What good looks like

  • The operators who keep accounts alive treat a warning as a hard stop, not noise. The mediocre version shrugs it off, keeps sending, and turns a warning into a restriction.
  • Consistency beats speed. Seven steady days outperform three aggressive ones: identical daily behavior is what makes the account look human, and rushed ramps are the number-one cause of verification prompts.
  • Engagement is not filler. The likes and comments in the early days are what makes the connection requests that follow look like a person, not a script. Skipping them to "save time" defeats the plan.
  • Done well, the account reaches 20 connection requests per day with zero verification prompts, and the first replies are already arriving from the day 5-7 conversations.

Rules

  • MUST pause 48-72 hours after any warning or verification prompt, then resume one level down.
  • MUST keep daily activity consistent; never compress two days of the ramp into one.
  • NEVER send identical messages across prospects; vary every message.
  • NEVER include a link before the prospect has replied.
  • NEVER skip the engagement activity (likes, comments) and run connection requests alone.

Read the full file on GitHub · 39 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. 9d ago First seen · 39 lines · 75 tokens per session scan A c05cb8c0c031

Subscribe to this mod's changes

linkedin-7-day-warmup is a skill published in the GitHub repository swan-gtm/gtm-skills (153 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 613 once invoked, about $0.0004 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-09-03.