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 skills/jayrha/agentskills/resume-writernpx skills add JayRHa/AgentSkills --skill resume-writergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/resume-writer)<a href="https://agentmods.dev/skills/jayrha/agentskills/resume-writer"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/resume-writer.svg" alt="Measured on agentmods" 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 | $0.00104 | $0.01258 |
| Opus 5 | $0.00052 | $0.00629 |
| Sonnet 5 | $0.00021 | $0.00252 |
| Haiku 4.5 | $0.00010 | $0.00126 |
Grade A, and why
resume-writer 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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Writer
Overview
This skill turns a messy work history into a focused, quantified, ATS-passable resume tailored to a specific target role. It optimizes for two readers at once: the applicant tracking system (keyword match, parseable structure) and the human recruiter who skims for ~7 seconds before deciding.
Keywords: resume, CV, curriculum vitae, ATS, job application, bullet points, professional summary, work experience, achievements, cover, career change, recruiter.
When to use vs. not
Use this to write, rewrite, restructure, or tailor a resume. This skill does not fabricate experience, invent metrics, or guarantee an interview — every claim must trace back to something the user actually did. When the user has no numbers, help them estimate honestly ("supported ~40 customers/week"), never invent precise figures.
Inputs to gather first
Ask only for what's missing; infer the rest:
- Target role + a job description (the single most important input — it drives keywords and emphasis).
- Work history: companies, titles, dates, and what they actually did/achieved.
- Education, certifications, key skills/tools.
- Seniority & career stage (student/new-grad, IC, manager, executive, career-changer).
- Region/format norms (US 1-page no-photo vs. EU CV vs. academic CV — see
references/format-by-region.md).
Workflow
- Pick the format. Reverse-chronological by default. Use functional/hybrid only for career changers or large gaps — and warn that ATS and recruiters distrust purely functional resumes. See
references/format-by-region.md. - Mine the job description. Extract the role's must-have keywords, tools, and outcomes. These become the vocabulary the resume must mirror (ATS matches on exact terms).
- Write the headline + summary. A 1-line title and a 2–3 line summary stating who they are, their strongest proof, and what they're targeting. No "results-oriented team player" filler.
- Rewrite every bullet with the impact formula.
Action verb + what you did + quantified result/context. Lead with the outcome when it's strong. Seereferences/bullet-formulas.mdand the verb bank. - Quantify relentlessly. Money, %, time, scale, frequency, or rank. If no hard number exists, use scope ("across 3 teams", "for a 12k-user platform").
- Order by relevance, not just recency. Within each role, put the bullets that match the target job first. Trim bullets older/irrelevant roles to 1–2 lines.
- Build the skills section from real, demonstrated skills that also appear in the JD. Group them (Languages / Tools / Domains). Don't list skills you can't defend in an interview.
- Tighten for ATS. Standard section headings, no tables/columns/text-boxes/images for the parsed version, real bullet characters, common fonts,
.docxor text-based PDF. Seereferences/ats-rules.md. - Cut to length. 1 page for <10 yrs experience, 2 pages otherwise (academic/EU CVs differ). Remove the objective, references-on-request, and anything pre-dating ~15 years unless pivotal.
- Proofread + tailor check. Consistent tense (past for past roles, present for current), parallel structure, zero typos. End with a gap analysis: which JD requirements the resume still doesn't address, and how the user might.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 63 lines · 104 tokens per session scan A 511aab705ffd
resume-writer is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,258 once invoked, about $0.0005 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-31.
Other skills, from other repositories
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…
design-director
Используй только внутри активного Codex Project Autopilot-проекта, когда уже выбрана проектная фаза и нужен design direction по плану автопилота.
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.
getting-started
Assess an authenticated Agiflow workspace and recommend the right next project-management workflow. Use when a user is new to Agiflow, asks what to do next, needs orientation, or is unsure whether to plan, refine, groom, triage, or review daily status.
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.