claude-linkedin-assistant: Command for Claude Code

.claude/commands/jobs/daily.md

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

A command that runs the job-search routine from start to finish. It checks setup, reviews the job tracker, finds jobs, and continues through the configured steps without asking between them.

In plain words
What is it for?
Use it as the normal daily entry point after setup. Individual job commands can still be run directly for one-off tasks.
Why use it?
It removes the need to start each daily job-search step separately or decide whether empty steps should be skipped. It also detects when the tracker is empty and starts with job discovery.

Command for Claude Code

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/farzamhejazik/claude-linkedin-assistant/daily"><img src="https://agentmods.dev/badge/commands/farzamhejazik/claude-linkedin-assistant/daily.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,050 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.01050
Opus 5 $0.00000 $0.00525
Sonnet 5 $0.00000 $0.00210
Haiku 4.5 $0.00000 $0.00105

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

Security

Grade A, and why

daily 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/daily.md · 104 lines

How it starts

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

DAILY (orchestrator)

/jobs daily is the main orchestrator. It runs the daily sequence end to end with no between-step prompts. Empty steps are auto-skipped.

For ad-hoc work, run individual /jobs <sub-command> directly. For normal use after /jobs setup, prefer /jobs daily.


How this command behaves

  1. Platform config check: read resumes/search_profile.md. If it has no ## Platforms section, run /jobs setup first (read and execute .claude/commands/jobs/setup.md). This only happens once — after setup writes the Platforms section, future daily runs skip this check.
  2. Run STEP 0 (Chrome + LinkedIn check from jobs.md) once at the start.
  3. Pre-flight: read job_tracker.csv. If it has 0 data rows (just the header), this is a first-run / empty-tracker state. Skip Step 1 (check) entirely — there's nothing to dashboard. Jump straight to Step 2 (find). Tell the user: "Tracker is empty, starting with discovery."
  4. Otherwise, walk through the steps below in order, end to end with no between-step prompts. Each step runs to completion, then the next one starts automatically. The user is not asked to continue between steps.
  5. Before each step, print a one-line preview of what's queued. If the queue is empty, auto-skip and announce.
  6. At the end, run the commit step automatically and print the daily summary.

If the user invokes a single sub-command from inside the daily flow (e.g. types /jobs outreach Walmart), exit the daily orchestrator and let that sub-command run standalone.


Step 1 — /jobs check (dashboard)

Skip if the tracker is empty (per the pre-flight check above — go straight to Step 2).

Otherwise: read check.md, execute. Show all sections. Continue to Step 2 automatically.


Step 2 — /jobs find (discover new jobs)

Read find.md. Surface candidate jobs based on the user's profile. Continue to Step 3 automatically.


Step 3 — /jobs add (capture finds)

For each job surfaced in Step 2, read add.md and add to the tracker. The find flow already auto-adds in batch — this step exists to handle anything the user wants to add manually that wasn't surfaced (e.g. a link they saw elsewhere).

Read the full file on GitHub · 104 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 · 104 lines · 0 tokens per session scan A bccd1e197167

Subscribe to this mod's changes

daily 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,050 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.