apply

A two-agent workflow for preparing a job application from a job posting. One agent drafts the application and another reviews it, using the posting supplied as a web address or pasted text.

In plain words
What is it for?
Use it to analyze a job posting, create application materials, review them for factual support, and update the candidate profile with confirmed skills, achievements, or project details.
Why use it?
It helps catch unsupported claims before an application is sent. It also records confirmed new facts in the candidate profile so later applications can use them.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/treymorgan/jobsearch-apply-mcp/apply
Clone the repo
git clone --depth 1 https://github.com/treymorgan/jobsearch-apply-mcp

Made for: Claude Code.

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 7,943 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin 86% 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 $0.00000 $0.07943
Opus 5 $0.00000 $0.03972
Sonnet 5 $0.00000 $0.01589
Haiku 4.5 $0.00000 $0.00794

Measured today against content hash 12347622b543, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

apply scanned grade A with 1 finding 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 today.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **If the fetch returns HTTP 403, or the content is a login wall or an unrelated listing page, do not give up and do not draft from the title.** Follow the escalation order in `.claude/skills/job-application-assistant/0
Origin

This is a copy

86% identical to apply — 52 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/apply.md · 381 lines

How it starts

The opening of the file, as written. The whole thing — 381 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.

Standing rule — write new facts back to the profile. If the user confirms, corrects or supplies a fact that is not already in 01-candidate-profile.md — a metric, a project detail, a skill, a scope correction — update that file in the same turn. Do not leave it living only in the conversation or in a draft.

This is not bookkeeping. A fact that exists only in chat will be treated as unsupported by a later session and stripped from drafts as a fabrication. Anything absent from the sources does not exist as far as future drafting is concerned, and the loss is silent — a real achievement quietly disappears from every subsequent CV.

This rule is the input side of the Step 3 Factual Grounding Audit, not a competitor to it. The audit is deliberately strict: an ungrounded claim is removed, and it cannot tell a fabrication from a real fact the user stated out loud last week. That strictness is correct, and it is exactly why confirmed facts have to reach the sources in the same turn they surface. Write to 01-candidate-profile.md specifically — it is one of the audit's three sources, so a fact recorded there is grounded on the next run. Adding a fact to 01 that CLAUDE.md and the master CV simply do not mention is an absence, not a contradiction, and does not trip the audit's profile-consistency warning; if the new fact corrects something either of those states, fix it there too rather than leaving the two sources disagreeing.

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 — page-break decisions are unpredictable, and source files that look fine often produce broken PDFs (orphaned entry titles, cover letters spilling to page 2, bullet fonts mismatching).

Read the full file on GitHub · 381 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. today First seen · 381 lines · 0 tokens per session scan A 12347622b543

Subscribe to this mod's changes

apply is a command published in the GitHub repository treymorgan/jobsearch-apply-mcp (0 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,943 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 86% identical to apply, differing in 52 lines, and is treated as a copy.