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/setupgit 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.00019 | $0.00996 |
| Opus 5 | $0.00010 | $0.00498 |
| Sonnet 5 | $0.00004 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00100 |
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 3d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Builder — One-Time Setup
Run this command once after installing the plugin to get started.
Input
$ARGUMENTS
Instructions
You are helping the user set up the Resume Builder plugin. Guide them through the steps below.
Step 1: Check Python
Run python --version (or python3 --version on Mac/Linux).
- If Python 3.10+ is installed, proceed to Step 2.
- If Python is NOT installed, tell the user:
The scoring engine requires Python 3.10 or later.
Download it from: https://www.python.org/downloads/
During installation:
- CHECK "Add Python to PATH" (Windows)
- Mac/Linux: Use your package manager (brew install python3)
After installing Python, run /resume-builder:setup again.
Stop here if Python is not installed.
Step 2: Choose Install Type
Ask the user which setup they prefer:
Option A: Quick Setup (Recommended for most users)
- Cloud-based scoring — no heavy downloads
- Installs only 2 small packages (~5 seconds)
- Scoring happens on our cloud server (5 free scores, then Pro $12/month for unlimited)
- Optional LLM-augmented scoring with your own Anthropic API key
Option B: Full Local Setup (For developers / offline use)
- Installs all scoring engines locally (~500MB, takes 2-3 minutes)
- Scoring runs on your machine — no cloud needed, no limits
- Requires more disk space and RAM
Step 3A: Quick Setup (Cloud)
pip install -r requirements-plugin.txt
If pip is not found, try pip3 or python -m pip. If needed, use the requirements-plugin.txt file from the installed plugin root.
This installs fastmcp (MCP protocol) and anthropic (for LLM features). All ATS/HR scoring goes through the cloud API automatically.
Step 3B: Full Local Setup
pip install -r requirements.txt
Use the requirements.txt file from the installed plugin root if needed. This takes 1-3 minutes (downloads sentence-transformers model ~80MB).
Then download NLTK data:
python -c "import nltk; nltk.download('wordnet'); nltk.download('punkt_tab')"
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.
- 3d ago First seen · 130 lines · 19 tokens per session scan A 569e7c3defff
setup is a command published in the GitHub repository jananthan30/Resume-Builder (77 stars, last pushed 18d ago), licensed MIT. It adds 19 tokens to every session and 996 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.