cv-make

A command that turns structured résumé data into a self-contained HTML résumé. The file can be opened in a browser and saved as a PDF.

In plain words
What is it for?
Use it to render the active resume.json through the selected template and prepare an ATS-friendly résumé for PDF export.
Why use it?
It removes the need for a separate document-generation tool and stops invalid or incomplete résumé data from producing a broken result.

Command

Install

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.

agentmods
npx agentmods add commands/localplugins/plugins/cv-make
Clone the repo
git clone --depth 1 https://github.com/localplugins/plugins
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 874 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00874
Opus 5 $0.00014 $0.00437
Sonnet 5 $0.00005 $0.00175
Haiku 4.5 $0.00003 $0.00087

Measured yesterday against content hash 007dee4c0c8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cv-make 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 yesterday.

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.

cv-forge/commands/cv-make.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/cv-make

Turn resume.json into a finished, ATS-friendly résumé. No Node at any point — a sh splice builds the HTML, and the browser (yours, via Save as PDF) does the actual rendering.

Steps

  1. Resolve the active résumé. Read resume.json from the repo root. If it's missing, tell the user to run /cv-new and stop.

  2. Resolve the active template. Read line 1 of cv/.active for the template slug (e.g. classic-ats). If cv/.active doesn't exist, default to classic-ats and mention that /cv-new normally sets this. Confirm the template exists at "${CLAUDE_PLUGIN_ROOT}/templates/<slug>/template.html" — if not, list the available slugs under templates/*/ and stop.

  3. Validate resume.json against the schema. Read ${CLAUDE_PLUGIN_ROOT}/schema/json-resume.schema.json and check the file the same way /cv-new does: basics and basics.name are required; basics.email (if present) must look like an email; every work[] needs name + position; every education[] needs institution; every skills[] needs name. Stop and report the exact bad field (e.g. education[0].institution is required) rather than rendering a broken résumé — don't guess or silently drop the offending entry.

  4. Splice the render. Run the literal splice script — pure sh + awk, no Node, no network:

    mkdir -p output
    slug="<kebab-case-of-basics.name>"   # Claude computes this, e.g. "Alex Rivera" -> "alex-rivera"
    sh "${CLAUDE_PLUGIN_ROOT}/lib/render.sh" \
      "${CLAUDE_PLUGIN_ROOT}/templates/<slug-of-template>/template.html" \
      "${CLAUDE_PLUGIN_ROOT}/templates/_shared/render-core.js" \
      resume.json > "output/resume-${slug}.html"
    

    This inlines the shared renderer and the résumé JSON straight into the template's two markers (/*__RENDER_CORE__*/, /*__RESUME_DATA__*/), producing one self-contained HTML file — no external <script src> or <link>, so it opens correctly from disk with no server. If sh isn't available for some reason, splice the same three pieces with your file tools instead: read the template, replace each marker line with the full contents of the corresponding file, and write the result — same output, same no-Node guarantee.

Read the full file on GitHub · 69 lines

Changes

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.

  1. yesterday First seen · 69 lines · 27 tokens per session scan A 007dee4c0c8b

Subscribe to this mod's changes

cv-make is a command published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 874 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-31.