ai-job-search: Command for Claude Code

.claude/commands/setup.md

setup is a command for Claude Code from MadsLorentzen/ai-job-search. It costs 0 tokens per session (6,275 once invoked), scanned A, original, MIT.

An onboarding workflow for an AI job-search framework. It collects a person’s professional information and fills the profile files needed by the job-application workflow.

In plain words
What is it for?
Use it to create or update a candidate profile, fill in professional details, or update one profile section for later job applications.
Why use it?
It prevents application drafting from starting with incomplete or scattered candidate information and checks where the project would publish before writing files.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is MadsLorentzen/ai-job-search's own configuration. It tells Claude Code how to work on ai-job-search 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 ai-job-search configures →

About the project

AI Job Search is a Claude Code-based framework that runs on a user's machine to organize an AI-assisted job application process. It evaluates job postings, adapts CVs, writes cover letters, and helps prepare for interviews. The catalogue entries define commands, skills, instructions, an agent, and a setting for this workflow.

MadsLorentzen/ai-job-search · 47,502 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to MadsLorentzen/ai-job-search. 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/MadsLorentzen/ai-job-search/master/.claude/commands/setup.md
Clone the repo
git clone --depth 1 https://github.com/MadsLorentzen/ai-job-search

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 setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/madslorentzen/ai-job-search/setup/github.svg)](https://agentmods.dev/commands/madslorentzen/ai-job-search/setup)
Your own site
<a href="https://agentmods.dev/commands/madslorentzen/ai-job-search/setup"><img src="https://agentmods.dev/badge/commands/madslorentzen/ai-job-search/setup/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 setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/madslorentzen/ai-job-search/setup"><img src="https://agentmods.dev/badge/commands/madslorentzen/ai-job-search/setup.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 6,275 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.06275
Opus 5.5 $0.00000 $0.02510
Sonnet 5.5 $0.00000 $0.01255
Haiku 4.5 $0.00000 $0.00628

Measured 7d ago against content hash 9f0a18014ece, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup 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 7d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • setup — 100% identical, 29 lines differ
  • setup — 89% identical, 83 lines differ
.claude/commands/setup.md · 442 lines

How it starts

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

/setup - Profile Onboarding

You are running the onboarding setup for the AI Job Search framework. Your goal is to collect the user's professional information and populate all profile files so the /apply workflow works out of the box.

There are three paths into setup. Step 0 picks the right one; all three converge on Step 3 (file generation) and Step 4 (confirmation).


Step 0: Welcome & Choose Path

If $ARGUMENTS contains --section <name>, skip directly to that section in Path C for an update-only flow. Do not run the path-selection prompt below.

Otherwise, first check where this working copy would publish to — before anything is written, not after (the Step 4 privacy note fires only once every file is already on disk, which is too late to inform the decision). Run git remote get-url origin; if the command fails (no remote, or not a git checkout), skip this check silently. If there is a GitHub origin, check it with gh repo view <owner/repo> --json visibility,isFork when gh is available. If the origin is a public fork of the template — or its visibility cannot be determined — warn now and wait:

Heads-up before we start: your origin points at <owner/repo>, which is a public GitHub fork. This setup writes your personal data (name, contact details, employment history, salary expectations) into tracked files, and anything you commit and push to that fork is visible to anyone. Two safe options: keep your profile commits local and never push them, or push to a private repository instead — SETUP.md section 8 has the two-minute private-remote recipe. Want to continue with the setup?

Wait for the user's confirmation before showing the path prompt. A private origin, no origin, or a non-fork remote needs no warning — continue silently.

Then, before greeting the user, scan the documents/ folder. Use Glob with documents/**/* and count files per subfolder (cv/, linkedin/, diplomas/, references/, projects/, applications/).

Read the full file on GitHub · 442 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. 7d ago Changed 9f0a18014ece
  2. 29d ago Changed · +5 lines 4d648949f79c
  3. 1mo ago Changed · +4 lines ee6ddee2adbc
  4. 1mo ago First seen · 433 lines · 0 tokens per session scan A 70e1136a6fcc

Subscribe to this mod's changes

setup is a command published in the GitHub repository MadsLorentzen/ai-job-search (47,502 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,275 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.