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 skills add suxrobGM/jobpilot --skill review-resumegit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/skills/suxrobgm/jobpilot/review-resume)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/review-resume"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/review-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/skills/suxrobgm/jobpilot/review-resume"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/review-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 18 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00983 |
| Opus 5.5 | $0.00011 | $0.00393 |
| Sonnet 5.5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
review-resume 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 28d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Resume
Save one improved version of a base resume as a Suggested rewrite variant. The user accepts or discards it in the dashboard. Never write to the base resume.
Runs after extract-resume on upload: extraction is faithful to the PDF, this pass makes the document better.
Setup
Follow ../_shared/setup.md, then:
jobpilot-api GET /api/resumes/$RESUME_ID
content: null → extraction hasn't run; say so and stop. Also Read the source PDF (path per ../_shared/setup.md) - extraction flattens two-column layouts and drops emphasis.
What to improve
For a human screener skimming, and the ATS parsing. Change only what's weak: where the candidate's own wording already works, keep it. Rewriting every line replaces their voice with one uniform voice, and that uniformity is what reads as generated.
summary- two or three plain sentences about what they actually work on and their strongest specifics. Don't open with " with N years of experience" or "Results-driven "; start from the work itself. Cut anything true of every candidate ("strong communicator", "team player").basics.headline- a role title people search for, not a slogan.- Bullets - past tense for past roles; a concrete verb, then what was built or changed. Replace "Responsible for" / "Worked on" / "Helped with" with what the person did. Lead with the result when there is one, but don't force every bullet into "Verb X, resulting in Y%": a resume where every line has the same shape reads as generated. Don't start most bullets with the same verb ("Developed", "Built"). Cut a phrase that repeats across entries - one stock phrase in three roles flattens all three.
- Projects - the same rules for
descriptionandbullets: say what it is and what it does, without "a robust, scalable platform". - Skill groups - consolidate. Past ~5 groups it reads as a keyword dump.
- Ordering - most relevant experience and projects first.
Avoid the phrases the server rejects in tailored resumes (listed in ../tailor-resume/SKILL.md, "Summary"): if the user accepts this rewrite, it becomes the base every tailored variant starts from.
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.
- 28d ago Changed 5c3e6327e609
- 1mo ago First seen · 64 lines · 28 tokens per session scan A 9fd71aa11270
review-resume is a skill published in the GitHub repository suxrobGM/jobpilot (101 stars, last pushed 21d ago), licensed MIT. It adds 28 tokens to every session and 983 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 skills, from other repositories
resume
Generate a tailored resume AND cover letter for a job description via the native four-role Resume Team, score both against ATS and HR rubrics, create DOCX files, and update the tracker. Use when the user pastes a job description and wants a complete application package (resume plus cover letter) with dual scoring and…
cover-letter
Create a compelling one-page, human-voice cover letter for a job description and generate the final DOCX. Use when the user wants a cover letter only (no resume), pastes a JD and asks for a letter, or needs a letter to accompany an already-tailored resume. Runs the mandatory humanvoiceaudit before producing the DOCX.
batch-resume
Process multiple job descriptions from the batchjds folder into tailored application packages, each produced by the native Resume Team, with independent candidate-fit gates and ordered DOCX and tracker writes. Use when the user has several JDs to run at once, drops files in batchjds, or asks for batch or bulk resume…
tailor-resume
Tailor a resume to a job description via the native four-role Resume Team, evidence-match it against the job's requirements, create a DOCX, and update the tracker. Use when the user pastes a job description and wants a tailored resume only (no cover letter), targeting an evidence match that covers every must-have with…
ww-upload-cover-letter
Upload a PDF cover letter from the coverletter/ folder (typically coverletter/Company-coverletter.pdf produced by ww-write-cover-letter) into a required WaterlooWorks Cover Letter document slot during the Full-Cycle Service Submit Application workflow. Use when a WaterlooWorks application package requires Cover…
ww-write-cover-letter
Create a tailored, one-page cover letter PDF named -coverletter.pdf in the coverletter/ folder, generated from a job description and one of the user's résumés and styled like their sample letter (Times font, centered bold name, address-left/links-right header). Use this whenever the user wants to write, draft…