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 check-best-practicesgit 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-best-practices)<a href="https://agentmods.dev/skills/dcassil/resume-kit/check-best-practices"><img src="https://agentmods.dev/badge/skills/dcassil/resume-kit/check-best-practices.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.00086 | $0.00708 |
| Opus 5 | $0.00043 | $0.00354 |
| Sonnet 5 | $0.00017 | $0.00142 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
check-best-practices 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
check-best-practices — generic best-practices score (read-only)
Baselining step 2 of original → base → structure → refine (RIT-I-0016). Runs
the generic, job-independent best-practices analyzer on the structurally
canonical resume and reports the findings. It is the read-only counterpart to
update-refine, which acts on these findings — this skill never edits the
resume.
Prerequisites
Run the shared Prerequisites gate — ../_shared/prerequisites.md.
- Required input: a
ResumeDocumentJSON — normally thestructureversion (run update-shape first);baseonly with a recorded shape-pass override. - Does NOT need a job. The best-practices score is job-independent.
- If no
structureexists yet: run update-shape first so the score reflects the structurally-canonical resume.
What it does
Run analyze-best-practices on the resume and present the BestPracticesReport.
Each finding carries a severity (per the RIT-A-0003 taxonomy) and a resolution
classification:
auto_suggestible— a concrete, truthful rewrite is available now (carried assuggested_change).needs_user_input— the fix requires a fact the system does not have (e.g. a real metric to quantify a bullet); carries anelicitation_prompt.
Group findings by resolution kind so the caller can see, at a glance, what update-refine can fix automatically vs what will require answering a question.
How to invoke
CLI
resume-tool analyze-best-practices --resume <structure.json> [--output {json,text,md}]
MCP tool: resume_analyze_best_practices. Input field: resume. There is no
job and no alias_file — the score is job-independent and deterministic across
every surface.
Output (BestPracticesReport)
Present the findings as-is: each finding's rule, severity, location, resolution
kind, and either its suggested_change (auto_suggestible) or elicitation_prompt
(needs_user_input). Do not apply any change — that is
update-refine's job. Do not blend these into a composite ATS score;
this is a standalone best-practices signal.
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 · 71 lines · 86 tokens per session scan A 61b665b6dbc6
check-best-practices is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 27d ago), licensed Apache-2.0. It adds 86 tokens to every session and 708 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.
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…