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/rank-changesnpx skills add dcassil/resume-kit --skill rank-changesgit 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/rank-changes)<a href="https://agentmods.dev/skills/dcassil/resume-kit/rank-changes"><img src="https://agentmods.dev/badge/skills/dcassil/resume-kit/rank-changes.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.00082 | $0.00982 |
| Opus 5 | $0.00041 | $0.00491 |
| Sonnet 5 | $0.00016 | $0.00196 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
rank-changes 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 3d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Renamed:
rank-changeswasrank-editsbefore v1.0.0 (see RIT-A-0005).
rank-changes - candidates -> rank-edit-candidates -> present
Purpose
The improve skills can produce several truthful candidate changes. This skill's
job is to rank those candidates with the deterministic preference-aware ranker
and present the best option(s) with reasons. It is the recommend half of the
preference-learning loop; learn-change records the outcome.
This skill does not edit a resume and does not bypass review. Any chosen
candidate must be represented as a ChangeProposal and sent through
open-edit-session -> session-prompt -> decide-change -> commit-session
before it reaches disk.
Prerequisites Gate
Run the shared prerequisites gate in
../_shared/prerequisites.md. Required inputs:
- A
ResumeDocumentJSON. - A
JobDescriptionJSON. - At least one truthful
Candidaterecord to rank. - A
FeatureContextfor those candidates. - The project
alias_filefromresume-kit/config.json, defaulting toresume-kit/learning/synonyms.jsonwhen present.
If candidates are missing, produce them first through update-keywords or update-terminology. Do not invent candidates in this skill.
Run Me In A Subagent
Ranking is read-only but may involve large candidate/context/history data. Hand
the subagent the candidate array JSON, FeatureContext JSON, optional
UserPreferenceProfile JSON, resolved alias_file, and this skill. The
subagent returns the ranked top candidates and reasons only.
Working Directory
resume-kit/
├── config.json
└── learning/
├── edit-feedback.jsonl
├── preferences.json
└── synonyms.json
Honor alias_file. Pass the same alias file used by match and
identify-gaps, so ranking and scoring see the same synonym universe.
Surfaces This Skill Drives
- CLI:
resume-tool rank-edit-candidates --candidates <candidates.json> --context <context.json> [--profile <preferences.json>] [--alias-file <path>] - MCP tool:
edit_candidates_rank - Facade capability:
rank-edit-candidates
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.
- 3d ago First seen · 104 lines · 82 tokens per session scan A 3b9a3a6cb008
rank-changes is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 23d ago), licensed Apache-2.0. It adds 82 tokens to every session and 982 once invoked, about $0.0004 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…