rank-changes

rank-changes is a skill for Claude Code, Codex from dcassil/resume-kit. It costs 82 tokens per session (982 once invoked), scanned A, original, Apache-2.0.

A ranking tool for choosing among truthful resume improvements. It orders possible changes according to preferences and explains the reasons, but does not edit the resume.

In plain words
What is it for?
Use it to rank keyword or terminology changes for a specific job description. It needs a parsed resume, job description, candidate changes, and their feature context.
Why use it?
It helps when several valid changes are available and you need to decide which one to review first. A separate approval process is still required before anything is saved.

Skill for Claude CodeCodex

Part of the resume-intelligence plugin — 31 skills, 1 command, 1 hook shipped together

Install

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.

agentmods
npx agentmods add skills/dcassil/resume-kit/rank-changes
Any agent
npx skills add dcassil/resume-kit --skill rank-changes
Clone the repo
git clone --depth 1 https://github.com/dcassil/resume-kit

Made for: Claude Code, Codex.

Or install resume-intelligence, the plugin that ships this one along with the rest of its 31 skills, 1 command, 1 hook.

Wrote 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.

agentmods badge for rank-changes

README.md
[![agentmods](https://agentmods.dev/badge/skills/dcassil/resume-kit/rank-changes.svg)](https://agentmods.dev/skills/dcassil/resume-kit/rank-changes)
Your own site
<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>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 982 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 3b9a3a6cb008, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/resume-intelligence/skills/rank-changes/SKILL.md · 104 lines

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-changes was rank-edits before 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 ResumeDocument JSON.
  • A JobDescription JSON.
  • At least one truthful Candidate record to rank.
  • A FeatureContext for those candidates.
  • The project alias_file from resume-kit/config.json, defaulting to resume-kit/learning/synonyms.json when 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

Read the full file on GitHub · 104 lines

Changes

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.

  1. 3d ago First seen · 104 lines · 82 tokens per session scan A 3b9a3a6cb008

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens