hr-reference-checking

hr-reference-checking is a skill for Claude Code, Codex from tuanductran/hr-skills. It costs 60 tokens per session (755 once invoked), scanned A, original, MIT.

A guide for conducting structured reference checks that verify a candidate’s past work and gather consistent feedback from managers, peers, or direct reports.

In plain words
What is it for?
Use it to create question sets, prepare candidates, run and document reference calls, interpret mixed feedback, combine references with interview results, and retain audit records.
Why use it?
It helps hiring teams collect useful evidence beyond interviews while handling reluctant or negative references consistently and within legal limits.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create question sets, prepare candidates, run and document reference calls, interpret mixed feedback, combine references with interview results, and retain audit records.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tuanductran/hr-skills/hr-reference-checking
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.

Any agent
npx skills add tuanductran/hr-skills --skill hr-reference-checking
Clone the repo
git clone --depth 1 https://github.com/tuanductran/hr-skills

Made for: Claude Code, Codex.

Its marketplace also offers this one on its own, as the plugin hr-reference-checking/plugin install hr-reference-checking after adding the marketplace above.

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 hr-reference-checking

README.md
[![agentmods](https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-reference-checking/github.svg)](https://agentmods.dev/skills/tuanductran/hr-skills/hr-reference-checking)
Your own site
<a href="https://agentmods.dev/skills/tuanductran/hr-skills/hr-reference-checking"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-reference-checking/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hr-reference-checking

Your own site · 80×15
<a href="https://agentmods.dev/skills/tuanductran/hr-skills/hr-reference-checking"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-reference-checking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 755 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00060 $0.00755
Opus 5 $0.00030 $0.00378
Sonnet 5 $0.00012 $0.00151
Haiku 4.5 $0.00006 $0.00076

Measured 9d ago against content hash 6db993dd3379, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

hr-reference-checking 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 9d 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.

skills/hr-reference-checking/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reference checking

Design and conduct structured reference checks that validate candidate claims, surface performance signal beyond the interview process, and stay legally sound across jurisdictions.

Supported tasks

  • Designing structured reference check question sets by role and level
  • Preparing candidates on how the reference process will work
  • Selecting the right references to request (manager, peer, direct report)
  • Conducting reference calls and documenting responses consistently
  • Handling reluctant, guarded, or "policy only confirms dates" references
  • Interpreting mixed or lukewarm references accurately
  • Escalating and handling a clearly negative reference
  • Complying with jurisdiction-specific reference-check and disclosure rules
  • Using back-channel references responsibly and ethically
  • Combining reference feedback with interview and assessment data
  • Documenting reference outcomes for audit and compliance purposes
  • Training hiring managers to conduct references consistently

Key prompts

Designing the process

  1. "Design a structured reference check question set for [role/level] covering performance, collaboration, and areas for development."
  2. "What references should we request for [role] — direct manager, peers, direct reports — and why?"
  3. "Draft guidance for candidates explaining how our reference check process works and what to expect."
  4. "How many references should we require for [role/level], and does that number change for senior or executive hires?"

Conducting the call

  1. "Write opening and closing scripts for a reference check call that build rapport and get candid answers."
  2. "How do I get useful signal from a reference who is only willing to confirm dates and title?"
  3. "Draft follow-up questions to ask when a reference gives a vague or generic positive answer."
  4. "How should the reference check approach differ for an internal mobility move versus an external hire?"

Interpreting results

  1. "How should I interpret a reference that is polite but notably lukewarm compared to the candidate's other references?"
  2. "What questions can distinguish a genuinely strong reference from a scripted, overly positive one?"
  3. "A reference raised a specific concern about [area] — how do we weigh this against strong interview performance?"
  4. "How do we compare conflicting signals when one reference is strongly positive and another is strongly negative?"

Read the full file on GitHub · 65 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 65 lines · 60 tokens per session scan A 6db993dd3379

Subscribe to this mod's changes

hr-reference-checking is a skill published in the GitHub repository tuanductran/hr-skills (58 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 755 once invoked, about $0.0003 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-09-03.

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

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens