cv-status

A command that reports the active résumé, its template, and the number of entries in each populated section. It also shows setup or PDF-export warnings when relevant.

In plain words
What is it for?
Use it to check the current résumé state, confirm the selected template, count work and education entries, and see whether setup is incomplete.
Why use it?
It gives a quick view of résumé configuration and content without opening every file or rendering the document.

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-status
Clone the repo
git clone --depth 1 https://github.com/localplugins/plugins
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 387 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.00031 $0.00387
Opus 5 $0.00015 $0.00193
Sonnet 5 $0.00006 $0.00077
Haiku 4.5 $0.00003 $0.00039

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

Security

Grade A, and why

cv-status 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-status.md · 40 lines

What it actually says

/cv-status

Show the current résumé state at any time — reuses the same emitters as the SessionStart hook, so the output matches what loads at session start, then adds a content summary the hook doesn't print.

Steps

  1. Set CV_FORGE_ROOT to the plugin root (${CLAUDE_PLUGIN_ROOT}), matching the hook's environment.

  2. From the repo root, run each emitter and print its output:

    for f in "${CLAUDE_PLUGIN_ROOT}"/lib/context/*; do bash "$f"; done
    

    The emitters cover: the active résumé (name, headline, template — from cv/.active), a setup nudge when nothing is configured yet, and a PDF preflight warning (only when the opt-in CV_FORGE_PDF export path is enabled). No network.

  3. If resume.json exists, read it directly (Claude reads JSON natively — no Node) and report section counts, e.g.:

    resume.json: basics ✓ (name, email, summary)
      work: 2 entries · education: 1 entry · skills: 4 entries
      projects: 1 entry · publications: 1 entry
    

    Only list sections that are present and non-empty; omit a section line entirely if it's missing or an empty array.

  4. If neither cv/.active nor resume.json exists, the setup-nudge emitter already told the user to run /cv-new — don't repeat it, just confirm there's nothing to summarize yet.

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 · 40 lines · 31 tokens per session scan A 4829a7698fa1

Subscribe to this mod's changes

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