Borrowing it
Nothing to install: this file belongs to tuanductran/hr-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tuanductran/hr-skills/main/.agents/skills/hr-root-router-maintaining/SKILL.mdgit 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-root-router-maintaining)<a href="https://agentmods.dev/skills/tuanductran/hr-skills/hr-root-router-maintaining"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-root-router-maintaining/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-root-router-maintaining"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-root-router-maintaining.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 169 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00066 | $0.02037 |
| Opus 5 | $0.00033 | $0.01019 |
| Sonnet 5 | $0.00013 | $0.00407 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
hr-root-router-maintaining 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 12d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HR root router maintenance
The root SKILL.md at the repository root is the entry point for the entire HR Skills library. It does not contain HR knowledge — its only job is to route requests to the right specialized skill package under skills/.
This skill tells AI assistants exactly how to update that router whenever the library changes.
Supported tasks
- Add a new skill entry to the correct routing section
- Remove a deprecated skill from the routing table
- Rename a skill entry when its directory is renamed
- Move a skill entry between routing sections
- Audit router for skills missing from the table or directories missing from
skills/ - Update the frontmatter
descriptionfield when new domains are added - Suggest which routing section a new skill belongs in
- Generate a complete, ready-to-paste router table row
- Validate that all
skills/<n>/SKILL.mdpaths resolve correctly
Router structure
The root SKILL.md has this layout — every edit must preserve it exactly:
frontmatter (---...---)
name: hr-skills
description: "..." ← update when adding an entirely new domain
metadata:
author: Tuan Duc Tran
version: "1.0.0" ← bump patch version on every router change
# HR Skills ← H1, never change
intro paragraph ← never change
## How to use this skill ← never change
numbered rules 1-5 ← never change
## Routing tables ← H2, never change
### <Section name> ← H3 section headers (see canonical list below)
| Skill | Use when... | ← routing table rows
...
## Notes ← H2, never change
Canonical routing sections
These are the current H3 section headers in order. New skills go into an existing section whenever possible. Only add a new H3 section when no existing one fits.
### Talent acquisition & recruiting### Onboarding, offboarding & people operations### Performance, talent & career management### Compensation, benefits & rewards### Learning & development### Organizational development, design & change### Workforce planning & analytics### HR technology, data & AI### Compliance, labor relations & risk### Culture, engagement, experience & wellbeing### Project management & global/local context### Software-engineering & technical hiring specialists
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.
- 12d ago First seen · 175 lines · 66 tokens per session scan A 928debd7ed5d
hr-root-router-maintaining is a skill published in the GitHub repository tuanductran/hr-skills (57 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 2,037 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-08-30.
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…