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 dcassil/resume-kit --skill update-terminologygit 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-terminology)<a href="https://agentmods.dev/skills/dcassil/resume-kit/update-terminology"><img src="https://agentmods.dev/badge/skills/dcassil/resume-kit/update-terminology.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.1 | $0.00094 | $0.01027 |
| Opus 5 | $0.00047 | $0.00513 |
| Sonnet 5 | $0.00019 | $0.00205 |
| Haiku 4.5 | $0.00009 | $0.00103 |
Grade A, and why
update-terminology 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 7d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
update-terminology - suggest -> edit session -> commit gate -> truth
Purpose
check-keywords and check-gaps score a resume against a job
deterministically. When the resume already demonstrates a required skill under a
different surface form, the employer's exact wording can be mirrored without
inventing a new claim.
This skill's create-change step turns those wording swaps into targeted
ChangeProposal records, then hands them to the shared change-application
runbook — the same decide → commit-gate → validate → learn spine used by
update-keywords. It does not directly edit the resume or bypass review.
To add a keyword the resume was missing but the master proves, use update-keywords. To surface a keyword absent from both this resume and the master/evidence, report a gap; never rewrite it in.
Prerequisites Gate
Run the shared prerequisites gate in
../_shared/prerequisites.md. Required inputs:
- A
ResumeDocumentJSON. - A
JobDescriptionJSON. - The project
alias_filefromresume-kit/config.json, defaulting toresume-kit/learning/synonyms.jsonwhen present.
If the resume or job JSON is missing, stop and run parse-resume or parse-job first.
Evidence precondition (required). Terminology swaps are truth-gated: the
accept path re-validates the swapped wording with validate_resume_truth
against the project's CandidateEvidence. With no evidence the gate cannot
substantiate any wording, so every swap is rejected (not applied) with the
reason "no candidate evidence — run extract-evidence first". Run
extract-evidence before this skill so the gate can substantiate the swaps;
a swap is only ever reported as applied when it passed the truth gate.
Run Me In A Subagent
This is a self-contained improve task over potentially large resume/job data.
Hand the subagent the active resume path, job path, resume-kit/config.json,
resolved alias_file, and this skill. The subagent returns only the proposed
and committed changes, skipped suggestions, gate results, and 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.
- 7d ago First seen · 103 lines · 94 tokens per session scan A a749c50eb2bb
update-terminology is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 27d ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,027 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
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…