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 tuanductran/hr-skills --skill hr-demand-planninggit clone --depth 1 https://github.com/tuanductran/hr-skillsWrote 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/tuanductran/hr-skills/hr-demand-planning)<a href="https://agentmods.dev/skills/tuanductran/hr-skills/hr-demand-planning"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-demand-planning/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.
<a href="https://agentmods.dev/skills/tuanductran/hr-skills/hr-demand-planning"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-demand-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00980 |
| Opus 5 | $0.00034 | $0.00490 |
| Sonnet 5 | $0.00014 | $0.00196 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
hr-demand-planning 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HR demand planning
Translate business strategy and operational plans into accurate headcount demand forecasts — from gathering demand signals and modeling capacity requirements to prioritizing critical roles and aligning recruiting resources.
Supported tasks
- Translating business plans into headcount demand models
- Gathering and validating demand signals from business leaders
- Modeling headcount requirements by role, level, and location
- Prioritizing critical hires against available recruiting capacity
- Designing demand intake and approval processes
- Building rolling demand forecasts with scenario modeling
- Aligning demand plans with budget and span-of-control targets
- Identifying demand volatility patterns and mitigation strategies
- Reporting demand vs. supply gaps to TA and HRBP partners
- Designing workforce demand review cadences with business stakeholders
- Connecting demand plans to recruiting pipeline and sourcing strategy
Key prompts
Demand signal gathering
- "Design a headcount demand intake process for [company] that gathers accurate signals from business leaders."
- "What questions should we ask business leaders to translate product or revenue growth into role-level headcount demand?"
- "How do we validate demand signals to avoid inflated headcount requests that drain recruiting capacity?"
- "Build a demand intake template for [department or function] that captures role, level, location, start date, and business justification."
- "How should HR business partners run quarterly demand planning conversations with their business unit leaders?"
Demand modeling
- "Model headcount demand for [department] growing from [current headcount] to [target] over [timeframe]."
- "What factors should drive a productivity-based headcount model for [function, for example, sales, engineering, support]?"
- "Design a scenario model that shows headcount demand under [conservative / base / aggressive] growth assumptions."
- "How do we account for attrition, internal transfers, and backfills when building a net new headcount demand model?"
- "What span-of-control ratios should we apply when modeling management headcount demand for [organization size]?"
- "How do we model headcount demand for a product launch with uncertain ramp timing?"
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.
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.
- 9d ago First seen · 75 lines · 68 tokens per session scan A c74639ca2b55
hr-demand-planning is a skill published in the GitHub repository tuanductran/hr-skills (57 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 980 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.
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…
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…
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…