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/tailor-resume)<a href="https://agentmods.dev/commands/jananthan30/resume-builder/tailor-resume"><img src="https://agentmods.dev/badge/commands/jananthan30/resume-builder/tailor-resume/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/tailor-resume"><img src="https://agentmods.dev/badge/commands/jananthan30/resume-builder/tailor-resume.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.00028 | $0.04768 |
| Opus 5 | $0.00014 | $0.02384 |
| Sonnet 5 | $0.00006 | $0.00954 |
| Haiku 4.5 | $0.00003 | $0.00477 |
Grade B, and why
tailor-resume scanned grade B with 2 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 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s -X POST http://localhost:8100/score/both -H "Content-Type: application/json" -d "{\"resume_path\": \"{configured_master_resume_path}\", \"jd_path\": \"applications/{folder}/job_description.txt\"}" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8100/health How it starts
The opening of the file, as written. The whole thing — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailor Resume Only — Native Four-Role Team
Optimize and tailor the resume using concurrent Codex shell and file operations for speed. Target: 75-85% ATS + 70%+ HR with AUTHENTIC content.
Job Description
$ARGUMENTS
CANDIDATE-FIT PREFLIGHT (MANDATORY FIRST GATE)
Before scorer startup, research, resume development, any role/native-team
invocation, output/application-directory creation, DOCX generation, or tracker
work, resolve master_resume_path from config.json and put this exact job
description in a private temporary UTF-8 file. Screen only that configured master
resume—never a previously tailored resume. Generate one safe run_id, one safe
case_id, and one strict ISO as_of_date, then run:
python candidate_fit_preflight.py --resume <configured-master-resume> --job-description <private-exact-JD.txt> --run-id <run_id> --case-id <case_id> --as-of-date <YYYY-MM-DD> --json
Require exit 0 and a valid candidate-fit-policy-v3 report bound to the same
IDs, date, master SHA-256, and exact-JD SHA-256. Canonically hash it as
candidate_fit_report_digest. Continue only with exact threshold 70.0, score at
least 70, trustworthy extraction, zero hard knockouts, passed: true, and no
codes. Exit 1, a score below 70 (including 60–69), or any hard knockout is
REJECTED:CANDIDATE_FIT; create no application directory, draft, DOCX, or tracker
row and invoke no role or native team. Exit 2 or an unavailable, malformed,
stale, non-canonical, or digest-mismatched report is
FAILED:CANDIDATE_FIT_PREFLIGHT and fails closed. There is no automatic or manual
workflow bypass. ATS and HR baselines are separate advisory diagnostics and cannot
override this gate.
Instructions
You are the coordinator, not the resume author. The user has provided a job description above. Execute the following phases, keeping independent scoring and file work concurrent where safe.
NATIVE RESUME TEAM (mandatory)
Only after candidate fit passes, read commands/resume-team.md, run its host
preflight, and invoke native_resume_team.py for the current host with the same
run/case IDs, as_of_date, exact private JD file, and a prospective non-existing
output path. Do not create the path first. Do not manually reproduce the role
sequence for a publishable draft. The runtime runs resume-researcher ->
resume-writer -> resume-auditor, then resume-editor only after FAIL, followed
by a fresh Auditor. It validates handoff digests, parents, distinct identities, and
replay state and allows at most two Editor corrections. The coordinator must not
author or silently repair resume prose. Require macOS or Linux; Windows preflight
fails closed with POSIX_RUNTIME_REQUIRED.
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.
- 10d ago First seen · 434 lines · 28 tokens per session scan B 5c7f23cd11bc
tailor-resume is a command published in the GitHub repository jananthan30/Resume-Builder (83 stars, last pushed 25d ago), licensed MIT. It adds 28 tokens to every session and 4,768 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
triage-inbox
Sort application mail into the freehire tracker and drain the link queues.
track
Record or update a job application in your local tracker so it shows on the Rebound dashboard.
rise
A supportive, practical check-in — momentum, next best action, and a plan that respects your runway. Knocked down, not out.
hunt
Run the autonomous daily hunt — source, triage, tailor, and file every new live role.
onboard
Set up or edit your dear-hiring-manager profile (identity, work authorization, EEO, screening answers) and register your resume.
job-search
Search live IT vacancies on freehire and shortlist the ones worth applying to.