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

.claude/commands/apply.md

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

A workflow that uses one agent to draft a job application and another to review it, based on a job posting supplied as a URL or pasted text.

In plain words
What is it for?
Use it to evaluate a posting, prepare a tailored CV and cover letter, get a content review, and verify the final application documents.
Why use it?
It separates writing from criticism and includes checks for the finished application, including compiling and inspecting PDF files.

Command for Claude Code

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

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 →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is cd ../cover_letters && xelatex -interaction=nonstopmode cover_<company>_<role>.tex.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/cypggs/ai-job-search-cn/apply"><img src="https://agentmods.dev/badge/commands/cypggs/ai-job-search-cn/apply.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,990 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.04990
Opus 5 $0.00000 $0.02495
Sonnet 5 $0.00000 $0.00998
Haiku 4.5 $0.00000 $0.00499

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

Security

Grade A, and why

apply 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/apply.md · 314 lines

How it starts

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

/apply - Drafter-Reviewer Job Application Workflow

You are orchestrating a two-agent job application workflow. The job posting is provided below as $ARGUMENTS (either a URL or pasted text).

Follow these steps exactly in order. Do not skip steps.

Token-efficiency rules for this workflow:

  • Never re-Read a file whose contents are already in your context from an earlier step. If you read it in Step 1, it is still available in Step 2.
  • When dispatching the reviewer agent, pass draft content inline in the agent prompt rather than asking the agent to Read files you already have in memory.
  • Run the full verification checklist exactly once, at the end (Step 6). The reviewer focuses on content critique, not verification.
  • Step 5 (compile and inspect PDFs) is mandatory and non-skippable — LaTeX page-break decisions are unpredictable, and .tex files that look fine often produce broken PDFs (orphaned entry titles, cover letters spilling to page 2, bullet fonts mismatching).

Step 0: Parse Input

  • If $ARGUMENTS looks like a URL, use WebFetch to retrieve the job posting content. Chinese job portals (BOSS 直聘, 拉勾, 猎聘, 智联招聘, 前程无忧) often block automated access; if WebFetch fails or returns a login/antibot page, ask the user to paste the job description text.
  • If it is pasted text, use it directly.
  • Extract: company name, role title, department (if mentioned), location, and language of the posting (Chinese or English).
  • Determine the target market: if the posting is in Chinese, targets a Chinese company, or uses Chinese salary conventions (e.g. 20k-30k·14薪), treat it as a China market application.
  • Store these for use throughout the workflow.

Step 1: DRAFTER - Evaluate Fit

Read the evaluation framework:

  • .claude/skills/job-application-assistant/04-job-evaluation.md
  • .claude/skills/job-application-assistant/01-candidate-profile.md

Using the framework from 04-job-evaluation.md, evaluate the job posting against the candidate's profile. If the salary lookup tool is configured, run:

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

Subscribe to this mod's changes

apply is a command published in the GitHub repository cypggs/ai-job-search-cn (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,990 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.