claude-linkedin-assistant: Command for Claude Code

.claude/commands/jobs/outreach.md

outreach is a command for Claude Code from FarzamHejaziK/claude-linkedin-assistant. It costs 0 tokens per session (2,957 once invoked), scanned A, original, MIT.

A job-search command that contacts people at a chosen company through LinkedIn. It sends connection requests to second-degree contacts and first messages to existing connections.

In plain words
What is it for?
Use it to start referral outreach for a selected company or for the most urgent pending company in a job-tracking file. Replies, follow-ups, and resume attachments remain manual.
Why use it?
It removes the need to choose outreach candidates and send these initial messages one by one. It also prioritizes companies whose referral deadlines are closest.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is FarzamHejaziK/claude-linkedin-assistant's own configuration. It tells Claude Code how to work on claude-linkedin-assistant itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-linkedin-assistant configures →

Reuse

Borrowing it

Nothing to install: this file belongs to FarzamHejaziK/claude-linkedin-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/FarzamHejaziK/claude-linkedin-assistant/main/.claude/commands/jobs/outreach.md
Clone the repo
git clone --depth 1 https://github.com/FarzamHejaziK/claude-linkedin-assistant

Made for: Claude Code.

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 outreach

README.md
[![agentmods](https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/outreach/github.svg)](https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/outreach)
Your own site
<a href="https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/outreach"><img src="https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/outreach/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 outreach

Your own site · 80×15
<a href="https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/outreach"><img src="https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/outreach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,957 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 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.00000 $0.02957
Opus 5 $0.00000 $0.01478
Sonnet 5 $0.00000 $0.00591
Haiku 4.5 $0.00000 $0.00296

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

Security

Grade A, and why

outreach 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 11d 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.

.claude/commands/jobs/outreach.md · 261 lines

How it starts

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

OUTREACH (cold sweep at a company)

The outreach flow does two things at a target company:

  1. Send connection requests to 2nd-degree contacts (recruiters, peers, leads). Always "Send without a note" — LinkedIn rate-limits personalized invites.
  2. Send a first DM to your existing 1st-degree connections at the company.

Out of scope (you handle these manually):

  • ❌ Replying to DMs once a thread is warm
  • ❌ Follow-up nudges on stale outreach
  • ❌ Sending a resume / file attachments

Step 1 — Pick a company

If the command was called with an argument (/jobs outreach Mixpanel), use that company. Skip the rest of this step.

Otherwise, read job_tracker.csv for outreach candidates: rows where Referral Needed=YES AND Referral StatusOutreach Pending / Connection Pending.

  • Has candidates → auto-pick the most urgent one: smallest Days Left (Referral Deadline − today; negative = overdue first). Tiebreaker: oldest Discovered Date. Print:

    Picked: <Company> — <Role> (deadline in <N> days)

    Proceed to Step 2 immediately. No confirmation prompt. (If you want to override, stop the run and re-invoke as /jobs outreach <OtherCompany>.)

  • No candidates in the tracker → ASK the user: "Tracker has no companies queued for outreach. Which company do you want to run outreach on? (You can also run /jobs find first to discover jobs.)" Wait for a company name, then proceed with that.

If the picked company is Connection Pending, jump to Step 4 — Check pending acceptances instead of Step 2.


Step 2 — Find contacts (1st-degree FIRST, then 2nd)

LinkedIn via Chrome:

  1. Navigate to https://www.linkedin.com/company/<slug>/people/. Extract the numeric company ID by scanning the page for urn:li:fsd_company:<id> and picking the most-frequent match.

  2. Step 2A (MANDATORY): 1st-degree only, no keyword filter:

    https://www.linkedin.com/search/results/people/?currentCompany=["<id>"]&network=["F"]
    

    Read every result. These are your existing connections at the company and are always the top picks for direct DMs.

Read the full file on GitHub · 261 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. 11d ago First seen · 261 lines · 0 tokens per session scan A 15bd1e5fb677

Subscribe to this mod's changes

outreach is a command published in the GitHub repository FarzamHejaziK/claude-linkedin-assistant (214 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,957 tokens. 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-30.