Shared instructions for the job-search commands. They define where the repository, resume files, search profile, and job-tracking file are located and which information each workflow should use.

Use it as the common reference for job discovery, outreach, and other job-search flows. It covers resume formats, target roles, skills, and search-profile settings.

It prevents different job-search commands from using inconsistent personal details, preferences, dates, or tracker locations. It also sets rules for handling missing resumes and optional search preferences.

How FarzamHejaziK/claude-linkedin-assistant configures Claude Code

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/_shared.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/_shared/github.svg)](https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/_shared)

Your own site

<a href="https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/_shared"><img src="https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/_shared/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/_shared"><img src="https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/_shared.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,743 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01743
Opus 5	$0.00000	$0.00872
Sonnet 5	$0.00000	$0.00349
Haiku 4.5	$0.00000	$0.00174

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

Security

Grade A, and why

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

.claude/commands/jobs/_shared.md · 134 lines

How it starts

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

Shared context — loaded by all /jobs sub-flows

Working directory: the cloned repo root (where job_tracker.csv lives). Today's date: read from system (YYYY-MM-DD).

User resume — the source of truth about WHO they are

Read whatever resume(s) the user has dropped into resumes/. Supported formats: .pdf, .tex, .md, .docx. Extract on demand:

Name (top of resume) — used by Step 0 LinkedIn verification.
Current title + employer + years experience + 2-3 specializations — used by /jobs outreach to build a third-person pitch sentence for the DM template.
Target job titles (resume headline + most recent role titles + role-aligned alternatives) — used by /jobs find searches.
Top skills / keywords (skills section + repeated terms across bullets) — used by /jobs find scoring.

If multiple resumes are present, read all of them and use the union. Never invent details that aren't on the resume.

If resumes/ is empty (only the README), stop the flow and tell the user to drop their resume in.

Search profile (optional) — the source of truth about WHAT they want

Look for resumes/search_profile.md. This is an OPTIONAL free-form file where the user writes their specific job-search preferences: must-haves, deal-breakers, interest areas, salary floors, location constraints, company-size preferences, anything that's not on the resume.

If it exists:

Read it as plain prose. No structured schema is enforced — it can be bullets, paragraphs, mixed.
Treat it as higher-priority signal than the resume when there's a conflict. The resume says what the user can do; the search profile says what they want to do.
Examples of how it shapes flows:
- "Remote only" → drop on-site results from /jobs find, even if the resume has a city in the contact line.
- "$200K minimum" → boost or filter on salary in the score.
- "Climate tech" → add to the keyword pool for searches and scoring.
- "No crypto" → exclude matching jobs entirely.
- "Senior IC, no people management" → drop manager-track titles.

Read the full file on GitHub · 134 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.

9d ago First seen · 134 lines · 0 tokens per session scan A 8fb63f6a561c

Subscribe to this mod's changes

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

Claude Code application-tracking automation career chrome-extension indeed

start-10-1

A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.

minicoohei/ai-agent-camp · 2 tokens

init

Initialize project documentation, preferences, or design tokens.

marcusgoll/Spec-Flow · 11 tokens

pseo-gbp-audit

Use when: kullanıcı "GBP audit", "Google Business Profile kontrol", "placeid eksik mi", "business listing kontrol", "harita listing audit", "google haritalar profili", "GMB audit", "local listing gap" der ya da /pseo-gbp-audit çağırırsa. Also use when: aktif projenin project.config.profiles array'inde "local-service"…

popiliadam/platinum-seo-engine · 231 tokens

claude-linkedin-assistant: Command for Claude Code