ai-job-search-cn: Command for Claude Code

.claude/commands/setup.md

setup is a command for Claude Code from cypggs/ai-job-search-cn. It costs 0 tokens per session (4,962 once invoked), scanned A, a copy of setup, MIT.

An onboarding workflow for collecting professional information and filling the profile files used by an AI job-search framework.

In plain words
What is it for?
Use it to build a profile from documents, enter information manually, update one section, or review existing files before generating profile data.
Why use it?
It prepares the information needed for evaluating jobs, tailoring applications, writing cover letters, and preparing for interviews.

Command for Claude Code

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

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

Reuse

Borrowing it

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

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/cypggs/ai-job-search-cn/setup/github.svg)](https://agentmods.dev/commands/cypggs/ai-job-search-cn/setup)
Your own site
<a href="https://agentmods.dev/commands/cypggs/ai-job-search-cn/setup"><img src="https://agentmods.dev/badge/commands/cypggs/ai-job-search-cn/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/cypggs/ai-job-search-cn/setup"><img src="https://agentmods.dev/badge/commands/cypggs/ai-job-search-cn/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 4,962 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 89% copy Near-identical to another mod 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.04962
Opus 5 $0.00000 $0.02481
Sonnet 5 $0.00000 $0.00992
Haiku 4.5 $0.00000 $0.00496

Measured 10d ago against content hash cd3a6e188119, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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

This is a copy

89% identical to setup — 70 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/setup.md · 413 lines

How it starts

The opening of the file, as written. The whole thing — 413 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, before greeting the user, scan the documents/ folder. Use Glob with documents/**/* and count files per subfolder (cv/, linkedin/, diplomas/, references/, applications/).

Then welcome the user with a single message that lists three paths. The wording changes based on what was found.

If documents/ has files in one or more subfolders, lead with Path A:

Welcome to the AI Job Search setup!

I'll help you build your professional profile so Claude can evaluate job postings, tailor CVs, write cover letters, and prepare you for interviews.

I see files in your documents/ folder: [list per subfolder, e.g. "2 in cv/, 1 in linkedin/, 3 in references/"]. Three ways to start:

Path A: Read my documents folder (recommended for what you have) - I'll read everything in documents/, cross-reference for consistency, and build your profile from real source materials. Idempotent and safe to re-run as you add more documents.

Path B: Single CV import - Paste or @-mention a single CV/resume here. I'll extract it and ask follow-up questions for what's missing.

Path C: Interview mode - I'll walk you through structured questions section by section.

Which would you like?

If documents/ is empty or missing, surface Path A as a "do this if you have materials" option:

Welcome to the AI Job Search setup!

I'll help you build your professional profile so Claude can evaluate job postings, tailor CVs, write cover letters, and prepare you for interviews.

Three ways to start:

Path A: Documents folder (best signal if you have several materials) - Drop your CV / LinkedIn export / diplomas / reference letters in the documents/ folder, then say "go". I'll read everything and build your profile from it. See documents/README.md for the folder layout.

Path B: Single CV import - Paste or @-mention a single CV/resume here. I'll extract it and ask follow-up questions for what's missing.

Path C: Interview mode - I'll walk you through structured questions section by section. Good if you're starting from scratch.

Which would you like?

Read the full file on GitHub · 413 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. 10d ago First seen · 413 lines · 0 tokens per session scan A cd3a6e188119

Subscribe to this mod's changes

setup is a command published in the GitHub repository cypggs/ai-job-search-cn (58 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,962 tokens. A static security scan graded it A with 0 findings. It is 89% identical to setup, differing in 70 lines, and is treated as a copy.