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/check-keywordsnpx skills add dcassil/resume-kit --skill check-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/check-keywords)<a href="https://agentmods.dev/skills/dcassil/resume-kit/check-keywords"><img src="https://agentmods.dev/badge/skills/dcassil/resume-kit/check-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.1 | $0.00095 | $0.01136 |
| Opus 5 | $0.00048 | $0.00568 |
| Sonnet 5 | $0.00019 | $0.00227 |
| Haiku 4.5 | $0.00010 | $0.00114 |
Grade A, and why
check-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 5d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renamed:
check-keywordswascheck-keyword-matchbefore v1.0.0 (see RIT-A-0005).
check-keywords — resume↔job keyword coverage
Prerequisites
Run the shared Prerequisites gate first — see
_shared/prerequisites.md.
- Required inputs (BOTH):
- a
ResumeDocumentJSON — theactive_resumepointer inresume-kit/config.json(or an explicit resume JSON path the caller passes). - a
JobDescriptionJSON — theactive_jobpointer inresume-kit/config.json(or an explicit job JSON path the caller passes).
- a
- If either is missing (no pointer, file absent, or a raw file where a
canonical JSON is required): STOP. Do not guess and do not run on partial
input. Tell the caller exactly which is missing and name the upstream skill:
- Missing/unconverted resume → run
parse-resumefirst. - Missing/unconverted job → run
parse-jobfirst.
- Missing/unconverted resume → run
Conversions are best run in subagents (large intermediate text stays out of the main context); pass the saved JSON paths back here.
Purpose
Answer one question: how much of the job's keyword set does this resume already cover, and which specific keywords are matched vs. missing? Use it to decide whether a resume needs alignment before applying, or to see exactly which job terms to address.
This is deliberately one job: keyword coverage only. It does not report a
composite/overall ATS score, section completeness, or structural parse issues
(that is check-structure), and it is distinct from the
missing/injectable keyword breakdown of check-gaps.
How to invoke
Prefer the MCP tool in-process; use the CLI when scripting.
CLI
resume-tool match --resume <resume.json> --job <job.json> \
[--alias-file <path>] [--output {json,text,md}] [--strict]
MCP tool: resume_check_job_match
Input fields: resume (serialized ResumeDocument), job (serialized
JobDescription), alias_file, strict.
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.
- 5d ago First seen · 108 lines · 95 tokens per session scan A b61c4a7726d5
check-keywords is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,136 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.