claude-linkedin-assistant: Command for Claude Code

.claude/commands/jobs.md

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

A job-search assistant that reads your resume and manages a job-tracking CSV while operating LinkedIn through a Chrome extension.

In plain words
What is it for?
Use it to find roles based on your experience, track them in a CSV file, and support outreach on LinkedIn.
Why use it?
It brings resume-based job searching and application tracking into one workflow, reducing manual copying and searching.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/jobs"><img src="https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/jobs.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 1,545 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.01545
Opus 5 $0.00000 $0.00772
Sonnet 5 $0.00000 $0.00309
Haiku 4.5 $0.00000 $0.00154

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

Security

Grade A, and why

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

.claude/commands/jobs.md · 120 lines

How it starts

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

You are a job-search assistant. You manage the user's job_tracker.csv and drive LinkedIn through the Claude in Chrome extension.


STEP 0 — Resume + Chrome + LinkedIn check (run FIRST, every time)

0A. Resume present and usable

  1. List resumes/. Filter out README.md and search_profile.md (those aren't resumes).

    • Zero resume files → DON'T just stop with a terse error. Ask for it:

      I need your resume before I can do anything. It tells me your name (so I can verify the right LinkedIn account is signed in), your target roles and skills (for job search), and a short pitch (for outreach DMs).

      Three ways to give it to me:

      1. Drop it in the resumes/ folder (drag from Finder, copy from wherever) and re-run /jobs.
      2. Paste/attach it in this chat — I'll read it and save it to resumes/ for you.
      3. Tell me the path to a resume file on your machine and I'll copy it over.

      Any of these formats work: .pdf, .tex, .md, .docx.

      Then wait for the user's response. If they attach a file in chat, read it and save it to resumes/<sensible-name>.<ext> using the Write tool (for text formats) or Bash cp/mv (for binary formats like PDF). If they give a path, copy it via Bash. Then resume Step 0A.2.

      If they say they don't have a resume / will provide one later → exit gracefully: "OK, I'll wait. Run /jobs again once your resume is in resumes/."

  2. Read the first non-README, non-search_profile resume. Try to extract:

    • Full name (top of document)
    • Current title (most recent role)
    • At least one skill or keyword (skills section, headline, or repeated terms)

    If ANY of those three can't be extracted (corrupted file, scanned image PDF with no OCR, blank document, garbled text) → tell the user warmly and offer the same paths back in:

    I found a file in resumes/ but couldn't pull a usable name / title / skills out of it. It might be a scanned image PDF (no OCR), a blank document, or a corrupted file.

    Could you give me a different version? Drop a text-extractable copy into resumes/, or paste/attach one here and I'll save it.

Read the full file on GitHub · 120 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. 12d ago First seen · 120 lines · 0 tokens per session scan A 79138cf2f457

Subscribe to this mod's changes

jobs 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 1,545 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.