jobsearch-apply-mcp: Command for Claude Code

.claude/commands/rank.md

rank is a command for Claude Code from treymorgan/jobsearch-apply-mcp. It costs 0 tokens per session (3,457 once invoked), scanned A, a copy of rank, MIT.

A batch job-ranking command that scores collected job postings against your profile and produces a shortlist.

In plain words
What is it for?
Use it to rank all new jobs, filter by a focus area, or re-rank jobs after changing your profile.
Why use it?
It helps you decide which new postings deserve detailed review and application effort. The scores are an initial triage, not a final evaluation.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

This is treymorgan/jobsearch-apply-mcp's own configuration. It tells Claude Code how to work on jobsearch-apply-mcp 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 jobsearch-apply-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/treymorgan/jobsearch-apply-mcp/main/.claude/commands/rank.md
Clone the repo
git clone --depth 1 https://github.com/treymorgan/jobsearch-apply-mcp

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 rank

README.md
[![agentmods](https://agentmods.dev/badge/commands/treymorgan/jobsearch-apply-mcp/rank/github.svg)](https://agentmods.dev/commands/treymorgan/jobsearch-apply-mcp/rank)
Your own site
<a href="https://agentmods.dev/commands/treymorgan/jobsearch-apply-mcp/rank"><img src="https://agentmods.dev/badge/commands/treymorgan/jobsearch-apply-mcp/rank/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 rank

Your own site · 80×15
<a href="https://agentmods.dev/commands/treymorgan/jobsearch-apply-mcp/rank"><img src="https://agentmods.dev/badge/commands/treymorgan/jobsearch-apply-mcp/rank.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 3,457 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% 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.03457
Opus 5 $0.00000 $0.01729
Sonnet 5 $0.00000 $0.00691
Haiku 4.5 $0.00000 $0.00346

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

Security

Grade A, and why

rank 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 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.

Makes network callslowCapability

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

- **Before marking anything `expired`, the agent must exhaust the escalation order** in `.claude/skills/job-application-assistant/09-web-research.md`: a `WebFetch` 403 is a rejected *client*, not a missing page, and retr
Origin

This is a copy

95% identical to rank — 81 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/rank.md · 148 lines

How it starts

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

/rank - Triage Scraped Jobs into a Ranked Shortlist

You are batch-scoring the jobs that /scrape has collected, so the user can decide where to spend /apply effort. /scrape finds and dedupes postings; /apply evaluates one at a time in depth. /rank is the bridge: it scores every new posting against the fit framework and returns a ranked shortlist.

/rank produces triage scores, not final evaluations. It scores from the posting text and the candidate profile only - no company research, no reviewer agent. /apply's Step 1 evaluation (which adds company research) remains authoritative and always re-runs when the user applies.

Follow these steps in order.


Step 0: Parse Input

$ARGUMENTS may contain:

  • Nothing → rank all jobs with status new in job_scraper/seen_jobs.json
  • A focus area (e.g. /rank data science) → rank only jobs whose title or stored fit-notes match the focus
  • --all → re-rank every job that has not been applied to, including previously ranked ones (useful after the profile changes)
  • --top <N> → shortlist size (default 5)

Step 1: Load State

  1. Read job_scraper/seen_jobs.json. If the file is missing or has no entries, tell the user to run /scrape first and stop.
  2. Read job_search_tracker.csv. Build the exclusion set: any company+role already in the tracker is out of scope regardless of flags - it has been applied to or consciously tracked.
  3. Select candidates: entries with status new (or entries of any status with --all), minus the exclusion set, filtered by the focus area if one was given.
  4. If no candidates remain, say so ("Nothing new to rank - run /scrape to find fresh postings") and stop.
  5. Read the scoring framework and profile once:
    • .claude/skills/job-application-assistant/04-job-evaluation.md
    • .claude/skills/job-application-assistant/01-candidate-profile.md

State how many jobs will be ranked before proceeding.


Step 2: Batch-Fetch and Score

Dispatch parallel general-purpose agents via the Agent tool, ~5 jobs per agent (a single agent is fine for ≤5 jobs). Token-efficiency rules, consistent with /apply:

Read the full file on GitHub · 148 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 · 148 lines · 0 tokens per session scan A 1cdd104e5df7

Subscribe to this mod's changes

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