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-structurenpx skills add dcassil/resume-kit --skill update-structuregit clone --depth 1 https://github.com/dcassil/resume-kitWhat 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.00097 | $0.00965 |
| Opus 5 | $0.00048 | $0.00483 |
| Sonnet 5 | $0.00019 | $0.00193 |
| Haiku 4.5 | $0.00010 | $0.00097 |
Grade A, and why
update-structure 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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
update-structure — original → base (structural check + auto-safe fix)
Baselining step 1 of the original → base → structure → refine pipeline (RIT-I-0016). This
skill gets the resume itself structurally ATS-clean before any job is
involved. It drives the deterministic build-base capability, whose fix is
auto-safe only and gated by claim-preservation (no employer/title/degree/
skill claim may be added, dropped, or altered).
Prerequisites
Run the shared Prerequisites gate — ../_shared/prerequisites.md.
- Required input: an active
originalResumeDocumentJSON — theactive_resumepointer inresume-kit/config.json. - Does NOT need a job. Baselining is job-independent.
- If the resume JSON is missing (no
active_resume, or a raw PDF/DOCX): STOP and run parse-resume first.
What it does
- Structural check. Run the deterministic resume-only structural check
(reuse check-structure) and present the
AtsStructureReport(section_completeness+recommendations). - Auto-safe base fix. Run
build-base(modeauto): it strips PII and placeholder text, normalizes dates/formatting, applies only deterministic, truth-preserving fixes, enforces the claim-preservation gate, writesresume-kit/resumes/<name>-base.json, and records thebasepointer. - Report applied vs deferred. Show which fixes were
appliedand which weredeferred(judgment / needs-input items). Deferred items are NOT fixed here — they are carried into the refine walkthrough (update-refine).
How to invoke
CLI
resume-tool check-structure --resume <original.json> [--output {json,text,md}]
resume-tool build-base --root . --mode auto [--output {json,text,md}]
MCP tools: resume_check_ats_structure, resume_build_base.
Modes (auto only — engine delta)
build-base is auto-only by design (RIT-T-0115): the fixes are deterministic
and truth-preserving, so there is no per-fix interactive approval at the base
stage. Interactive, human-in-the-loop handling of the deferred judgment items
happens in the next step, update-refine (the refine walkthrough).
Do not claim this skill applies interactive base fixes; it applies the auto-safe
set and defers the rest.
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.
- 2d ago First seen · 86 lines · 97 tokens per session scan A d2e218fbd39b
update-structure is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 97 tokens to every session and 965 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…