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.
curl -O https://raw.githubusercontent.com/FarzamHejaziK/claude-linkedin-assistant/main/CLAUDE.mdgit clone --depth 1 https://github.com/FarzamHejaziK/claude-linkedin-assistantWrote 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/instructions/farzamhejazik/claude-linkedin-assistant/claude-md)<a href="https://agentmods.dev/instructions/farzamhejazik/claude-linkedin-assistant/claude-md"><img src="https://agentmods.dev/badge/instructions/farzamhejazik/claude-linkedin-assistant/claude-md/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/instructions/farzamhejazik/claude-linkedin-assistant/claude-md"><img src="https://agentmods.dev/badge/instructions/farzamhejazik/claude-linkedin-assistant/claude-md.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.01965 | $0.01965 |
| Opus 5 | $0.00983 | $0.00983 |
| Sonnet 5 | $0.00393 | $0.00393 |
| Haiku 4.5 | $0.00197 | $0.00197 |
Grade A, and why
claude-linkedin-assistant CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Claude LinkedIn Assistant
Project rules loaded automatically when Claude works in this folder.
What this is
A minimal job-search workspace that pairs job_tracker.csv with a Claude-driven daily orchestrator. The intended user path is simple: run /jobs setup once to configure the workspace, then run /jobs daily to check the tracker, find jobs, add strong matches, run referral outreach, and commit the day's work. Status edits are done by hand directly in the CSV.
See README.md for the user-facing overview and REQUIREMENTS.md for setup. The authoritative command flows live in .claude/commands/jobs/.
Primary workflow
Default to the simple path unless the user asks for a specific sub-command:
/jobs setup— first-run setup and platform configuration./jobs daily— main orchestrator for day-to-day use.
/jobs daily is the recommended entry point after setup because it reduces user burden. It decides what to run next, skips empty steps, runs discovery, adds qualified jobs, runs outreach when needed, and commits once at the end.
Use individual flows (check, find, add, outreach, indeed-setup) for ad-hoc requests or when the user explicitly asks for that narrower action.
Where the docs live (read before acting)
| File | Purpose |
|---|---|
CLAUDE.md (this file) |
Project-wide hard rules, canonical values |
README.md |
Human-readable workflow overview |
REQUIREMENTS.md |
Setup (Chrome extension, git) |
.claude/commands/jobs/_shared.md |
Shared rules loaded by every /jobs sub-flow |
.claude/commands/jobs/{setup,find,check,add,outreach,daily,indeed-setup}.md |
Per-flow procedures |
resumes/ |
User's resume(s). Source of truth for name, target roles, skills, pitch |
resumes/search_profile.md |
(Optional) free-form preferences + platform config (LinkedIn/Indeed opt-in). Overrides resume-inferred defaults during /jobs find. |
User resume — the source of truth
This repo has no separate profile file. Everything Claude needs about the user comes from their resume in resumes/. Read whatever's there (PDF / .tex / .md / .docx) whenever a flow needs:
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.
- 11d ago First seen · 103 lines · 1,965 tokens per session scan A afcb2bf00ce5
claude-linkedin-assistant CLAUDE.md is an instructions file published in the GitHub repository FarzamHejaziK/claude-linkedin-assistant (214 stars, last pushed 3mo ago), licensed MIT. It adds 1,965 tokens to every session, about $0.0098 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).