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/dcassil/resume-kit/update-keywordsnpx skills add dcassil/resume-kit --skill update-keywordsgit clone --depth 1 https://github.com/dcassil/resume-kitWrote 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/dcassil/resume-kit/update-keywords)<a href="https://agentmods.dev/skills/dcassil/resume-kit/update-keywords"><img src="https://agentmods.dev/badge/skills/dcassil/resume-kit/update-keywords.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.00112 | $0.01146 |
| Opus 5 | $0.00056 | $0.00573 |
| Sonnet 5 | $0.00022 | $0.00229 |
| Haiku 4.5 | $0.00011 | $0.00115 |
Grade A, and why
update-keywords 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renamed:
update-keywordswasinject-keywordsbefore v1.0.0 (see RIT-A-0005).
update-keywords - injectable gaps -> edit session -> commit gate -> truth
Purpose
check-gaps scores a resume against a job deterministically. It splits
missing JD keywords into two buckets:
- Injectable - missing from this resume, but proven by the master resume or evidence. Surfacing it into this resume is truthful.
- Non-injectable - absent from both this resume and the master/evidence. This is a real gap, not an edit candidate.
This skill's job is the create-change step: turn injectable keywords into
targeted ChangeProposal records. It then hands those records to the shared
change-application runbook, which owns the decide → commit-gate → validate → learn
spine. The skill does not bulk-edit resume JSON.
Distinct from update-terminology, which only swaps wording for a keyword the resume already satisfies under an alias. Here we add a true, missing keyword to an appropriate summary, skills, or evidence-backed accomplishment surface.
Prerequisites Gate
Run the shared prerequisites gate in
../_shared/prerequisites.md. Required inputs:
- A
ResumeDocumentJSON: active resume fromresume-kit/config.json, or an explicit path. - A
JobDescriptionJSON: active job fromresume-kit/config.json, or an explicit path. - A gap result from check-gaps, including the injectable and non-injectable split.
- The master resume/evidence used to prove each injectable keyword.
If any required input is missing, stop and name the upstream skill:
- Need a resume JSON -> run parse-resume.
- Need a job JSON -> run parse-job.
- Need the injectable split -> run check-gaps.
- Need evidence records -> run extract-evidence or persist a user
confirmed statement with
resume-tool add-evidence --confirmed --content ....
Run Me In A Subagent
This is a self-contained improve task over potentially large resume/job/evidence
data. The main agent should hand the subagent the active resume path, job path,
master/evidence path, gap result, resume-kit/config.json, and this skill. The
subagent returns only the proposed/applied change summary, skipped gaps, gate
results, and before/after score deltas.
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 · 112 lines · 112 tokens per session scan A 000ebc5595b3
update-keywords is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 24d ago), licensed Apache-2.0. It adds 112 tokens to every session and 1,146 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…