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.
git clone --depth 1 https://github.com/jananthan30/Resume-BuilderWrote 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/jananthan30/resume-builder/find-jobs)<a href="https://agentmods.dev/commands/jananthan30/resume-builder/find-jobs"><img src="https://agentmods.dev/badge/commands/jananthan30/resume-builder/find-jobs/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/jananthan30/resume-builder/find-jobs"><img src="https://agentmods.dev/badge/commands/jananthan30/resume-builder/find-jobs.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.00018 | $0.01344 |
| Opus 5.5 | $0.00007 | $0.00538 |
| Sonnet 5.5 | $0.00004 | $0.00269 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
find-jobs 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Jobs — Discover & Score
Search live job boards for roles that match your resume, scored and ranked by fit.
Input
$ARGUMENTS
Instructions
You are helping the user discover relevant job opportunities scored against their resume using the discover_jobs MCP tool. Follow this workflow precisely.
Step 1: Read Master Resume
Read config.json to get master_resume_path. Extract the full resume text:
.docxfiles: use theextract_textMCP tool.pdf,.md,.txtfiles: read directly
If config.json is missing or master_resume_path is not set, ask the user to paste their resume text directly.
Step 2: Parse the Search Query
From $ARGUMENTS, extract:
- Job title: the role to search for (e.g., "Senior Data Scientist", "Clinical Research Associate")
- Location: city, state, or country if mentioned (e.g., "New York", "Boston", "remote")
- Remote preference: if the user said "remote" or "remote only"
If the user provided no arguments at all, do NOT ask. Proceed with empty job_title — the AI will analyze the resume and suggest search terms automatically.
Examples of valid inputs:
Senior Data Scientist in New YorkClinical Research Associate BostonSoftware Engineer remoteMedical Director(no location)- (blank) — AI analyzes resume and picks the best search
Step 3: Call discover_jobs
Call the discover_jobs MCP tool with:
resume_text: full resume text from Step 1job_title: extracted from Step 2 (empty string if none given)location: extracted from Step 2 (empty string if none)remote_only: true if user said remote only, false otherwisemax_results: 10
Step 4: Handle Errors
If setup_required is true (no API keys):
Show this message exactly:
Job discovery needs API keys to search live job boards.
Option 1 — Cloud (easiest, no setup):
Sign up at https://getresumehq.com
Then run /resume-builder:setup to link your account.
Option 2 — Local (free):
Get free Adzuna keys at https://developer.adzuna.com/
Add to your .env file:
ADZUNA_APP_ID=your_app_id
ADZUNA_APP_KEY=your_app_key
Remotive (remote jobs only) works without any key.
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.
- 1mo ago First seen · 135 lines · 18 tokens per session scan A ed79a99fa595
find-jobs is a command published in the GitHub repository jananthan30/Resume-Builder (87 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,344 once invoked, about $0.0001 per session on Opus 5.5. 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.
Other commands, from other repositories
job-search
Search live IT vacancies on freehire and shortlist the ones worth applying to.
tailor-cv
Reframe a CV toward one vacancy, citing evidence for every claim.
triage-inbox
Sort application mail into the freehire tracker and drain the link queues.
market-fit
Score a stack against live vacancy demand and name the gaps worth closing.
track-applications
Review where every application stands and bring the tracker up to date.
start
Onboard with Rebound — capture your base resume and build your private profile (skills, differentiators, and situation).