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 zhiweio/resume-as-code --skill resume-generationgit clone --depth 1 https://github.com/zhiweio/resume-as-codeWrote 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/zhiweio/resume-as-code/resume-generation)<a href="https://agentmods.dev/skills/zhiweio/resume-as-code/resume-generation"><img src="https://agentmods.dev/badge/skills/zhiweio/resume-as-code/resume-generation/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/zhiweio/resume-as-code/resume-generation"><img src="https://agentmods.dev/badge/skills/zhiweio/resume-as-code/resume-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.03875 |
| Opus 5 | $0.00028 | $0.01937 |
| Sonnet 5 | $0.00011 | $0.00775 |
| Haiku 4.5 | $0.00006 | $0.00387 |
Grade A, and why
resume-generation 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 9d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Generation
Produce one tailored resume in YAML for a single Job Description, by combining the candidate's master timeline with JD-specific analysis. The result is validated and placed under data/resumes/.
When to trigger
Activate when the user supplies a Job Description (raw text, a link, or a file path) and asks for a resume, a tailored resume, or a resume for that role.
Inputs you must read
data/profiles/basics.ymldata/profiles/education.ymldata/profiles/certificates.yml- All files under
data/timeline/*.yml - The user-provided JD
Outputs you will produce
- Intermediate artifacts in
data/.cache/<UTC-Timestamp>/(one per generation run). - Final resume in
data/resumes/{CandidateName}_{JobTitle}_{Company}.yml.
Review & Revision Options
Before starting the pipeline, present the user with these options:
- Auto review + revise — should the pipeline automatically review and revise the resume after De-AI? (default:
yes) - Revision rounds — how many review-revise cycles to run? (default:
1, options:1/2/3) - yamlresume compatibility — should the final output pass
pnpm yamlresume validate? (default:no)
Present as a single prompt:
Resume generation pipeline ready. Quick setup:
- Auto review & revise after generation? [Y/n]
- Review-revise rounds? [1/2/3] (default: 1)
- yamlresume format compatibility? [y/N] (default: no)
If the user does not respond, use defaults (yes, 1, no). Store the answers in the run context for steps 5 and 10.
Format routing:
- yamlresume compatible =
yes→ generate in Legacy (YAMLResume) format. Use assets/resume.example.yml as the structural template for step 6, andassets/section-*.example.ymlfor step 5. - yamlresume compatible =
no→ generate in New Schema v1.0 format. Use assets/resume-new-schema.example.yml as the structural template for step 6, andassets/section-*.new-schema.example.ymlfor step 5.
What ships with it
25 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.
- assets/company-business-analysis.example.yml 1.4 KB
- assets/jd.example.txt 2.8 KB
- assets/job-analysis.example.yml 1.9 KB
- assets/resume-new-schema.example.yml 4.8 KB
- assets/resume.example.yml 5.4 KB
- assets/review.example.yml 7.7 KB
- assets/section-personal-summary.example.yml 427 B
- assets/section-personal-summary.new-schema.example.yml 475 B
- assets/section-projects.example.yml 575 B
- assets/section-projects.new-schema.example.yml 614 B
- assets/section-skills.example.yml 510 B
- assets/section-skills.new-schema.example.yml 635 B
- assets/section-work.example.yml 1.4 KB
- assets/section-work.new-schema.example.yml 1.5 KB
- references/company-business-analysis.md 6.6 KB
- references/humanizer-en.md 25 KB
- references/humanizer-zh.md 15 KB
- references/job-analysis.md 7.2 KB
- references/overview.md 7.8 KB
- references/resume-review.md 7.6 KB
- references/resume-revision.md 9.7 KB
- references/section-personal-summary.md 4.5 KB
- references/section-projects.md 3.9 KB
- references/section-skills.md 3.4 KB
- references/section-work.md 7.4 KB
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.
- 9d ago First seen · 264 lines · 57 tokens per session scan A 966f69b5c860
resume-generation is a skill published in the GitHub repository zhiweio/resume-as-code (89 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 3,875 once invoked, about $0.0003 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 skills, from other repositories
cv-resume-builder
Optimize resumes and CVs for impact, ATS compatibility, and audience targeting. Supports multiple formats (chronological, functional, hybrid), accomplishment framing (STAR/XYZ), and tailoring for specific roles. Triggers on resume review, CV update, job application prep, or career document requests.
apply-high-performer-retention
Use when a manager wants to proactively retain top-performing direct reports — because high performers have the most options to leave and require active, differentiated management attention to stay engaged and challenged.
run-career-conversation
Use when a manager wants to have a structured career development conversation with a direct report — separate from weekly one-on-ones and performance reviews — to understand their long-term aspirations, identify growth gaps, and create a concrete development plan.
run-reference-check
Use when evaluating a finalist candidate for a role — to conduct structured phone reference calls that surface specific performance evidence, development needs, and potential red flags that interviews cannot reveal.
write-role-scorecard
Use when defining a role before hiring for it — to specify the outcomes the new person must achieve, the competencies required to achieve them, and the cultural requirements, so that interview questions target evidence of actual job performance rather than proxies like credentials or experience.
run-behavioral-interview
Use when conducting a job interview — to ask structured behavioral questions using the STAR method so that candidate evaluation is based on demonstrated past behavior rather than self-reported traits or hypothetical answers.