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.
npx agentmods add commands/jananthan30/resume-builder/find-jobsgit clone --depth 1 https://github.com/jananthan30/Resume-BuilderWhat 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 | $0.00018 | $0.01344 |
| Opus 5 | $0.00009 | $0.00672 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 135 lines · 18 tokens per session scan A ed79a99fa595
find-jobs is a command published in the GitHub repository jananthan30/Resume-Builder (76 stars, last pushed 17d ago), licensed MIT. It adds 18 tokens to every session and 1,344 once invoked, about $0.0001 per session on Opus 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
apply
You are orchestrating a two-agent job application workflow. The job posting is provided below as $ARGUMENTS (either a URL or pasted text).
setup
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.
outcome
You are recording what happened to a job application: progress updates (interview invitations, stages completed, offers) and final resolutions (hired, rejected, no response). The data lands in two places the framework already reads but nothing systematically writes.
add-portal
You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic linkedin-search and freehire-search), and the README invites users elsewhere to build equivalents — this command turns that invitation…
add-template
You are helping the user register their own CV or cover letter template with the AI Job Search framework — LaTeX, Typst, or any other toolchain that compiles to PDF from the command line. The framework ships with moderncv (banking style) for CVs and a custom cover.cls for cover letters. This command lets the user swap…
gmail-sync
You are scanning the user's Gmail for status signals on tracked job applications (interview invites, assessment links, offers, rejections) and, once approved, writing the detected changes into jobsearchtracker.csv and documents/applications/ /outcome.md - the same two places /outcome writes to, in the same schema.