Borrowing it
Nothing to install: this file belongs to treymorgan/jobsearch-apply-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/treymorgan/jobsearch-apply-mcp/main/.claude/commands/setup.mdgit clone --depth 1 https://github.com/treymorgan/jobsearch-apply-mcpWrote 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.
[](https://agentmods.dev/commands/treymorgan/jobsearch-apply-mcp/setup)<a href="https://agentmods.dev/commands/treymorgan/jobsearch-apply-mcp/setup"><img src="https://agentmods.dev/badge/commands/treymorgan/jobsearch-apply-mcp/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.
<a href="https://agentmods.dev/commands/treymorgan/jobsearch-apply-mcp/setup"><img src="https://agentmods.dev/badge/commands/treymorgan/jobsearch-apply-mcp/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.06154 |
| Opus 5 | $0.00000 | $0.03077 |
| Sonnet 5 | $0.00000 | $0.01231 |
| Haiku 4.5 | $0.00000 | $0.00615 |
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 476 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).
Apply the question-progress standing rule in AGENTS.md throughout this
workflow: path selection, document conflicts, gap-filling follow-ups and
optional sections are all part of one interview sequence, so each gets a
counter. Where Path A's follow-ups depend on what the documents turn out to
contain, say more may follow rather than inventing a total.
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, start with a short orientation about where the answers will be written, before anything is written, not after.
Your personal answers are written to two locations that are gitignored, so they are never committed even if this working copy is a public fork:
profile/at the workspace root: your candidate profile, behavioral profile, job evaluation preferences, interview examples andCLAUDE.mdoverview.jobsearch.config.jsonat the workspace root: your search terms, target locations and salary floor.
The files under .claude/skills/job-application-assistant/ are blank templates that
stay tracked. Read them for structure; never write the user's real details into them.
The same applies to cv/main_example.tex and cover_letters/cover_example.tex, which
are shipped samples: write the user's real CV to cv/main_<name>.tex, which is
gitignored.
Do a quick sanity check that this protection is actually in place. Run
git check-ignore -q profile/ jobsearch.config.json; if it exits non-zero, the ignore
rules are missing or have been edited, so warn and wait:
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.
- 8d ago First seen · 476 lines · 0 tokens per session scan A 3070a9103e9e
setup is a command published in the GitHub repository treymorgan/jobsearch-apply-mcp (0 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,154 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-31.
Other commands, from other repositories
quick-eval
Quick job evaluation. Paste a JD and get a score plus one-paragraph summary. Faster than a full evaluate. Use when someone says 'quick eval', 'quick score', or 'just give me a number'.
upskill
Find the skill gaps that keep recurring across your applications and turn them into a learning plan.
detect-ats
Work out which ATS a company uses, and what that means for your CV.
plan-content
Plan or draft LinkedIn posts under the 360Brew rules.
rise
A supportive, practical check-in — momentum, next best action, and a plan that respects your runway. Knocked down, not out.
profile
View or update your Rebound profile — skills, differentiators, and your private situation (work authorization, timeline).