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-cloudgit 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-cloud)<a href="https://agentmods.dev/skills/tuanductran/hr-skills/hr-cloud"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-cloud/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-cloud"><img src="https://agentmods.dev/badge/skills/tuanductran/hr-skills/hr-cloud.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.00067 | $0.00774 |
| Opus 5 | $0.00034 | $0.00387 |
| Sonnet 5 | $0.00013 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
hr-cloud 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 10d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HR cloud hiring
Helps HR and technical recruiters hire for cloud engineering, DevOps, and cloud architecture roles, translating cloud technical requirements into job descriptions, interview processes, and assessment criteria non-specialist recruiters can use confidently.
Supported tasks
- Writing job descriptions for cloud engineer, DevOps, SRE, and cloud architect roles
- Creating technical screening questions for cloud roles at different seniority levels
- Building a leveling framework distinguishing junior, mid, senior, and staff cloud roles
- Designing a technical interview loop and scorecards for cloud hiring
- Translating cloud certifications (AWS, Azure, GCP) into résumé screening criteria
- Drafting take-home or live coding/architecture exercises for cloud roles
- Creating a glossary of cloud terminology for non-technical recruiters
- Building a skills matrix comparing candidates across cloud platforms
- Drafting compensation benchmarking guidance for cloud roles by seniority
- Designing onboarding plans for new cloud engineering hires
- Creating reference-check questions focused on production incident experience
- Building a sourcing strategy for niche cloud specialties (e.g., FinOps, platform engineering)
Key prompts
Job descriptions and leveling
- "Write a job description for a [seniority level] Cloud Engineer focused on [AWS/Azure/GCP]."
- "Build a leveling framework distinguishing junior, mid, senior, and staff cloud engineers."
- "Draft a job description for a Site Reliability Engineer role with [on-call expectations]."
- "Explain what distinguishes a Cloud Architect from a Cloud/DevOps Engineer for a recruiter."
- "Create a glossary of key cloud terms (IaC, containers, CI/CD) for non-technical recruiters."
Screening and interviewing
- "Create screening questions to assess [seniority] level cloud experience in a first-round call."
- "Draft a technical interview loop structure for a Cloud Engineer role, including panel focus areas."
- "Design a live system-design exercise appropriate for a senior cloud architecture interview."
- "Create an interview scorecard rubric covering infrastructure-as-code, scalability, and security topics."
- "Draft reference-check questions focused on a candidate's production incident response experience."
What ships with it
3 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.
- 10d ago First seen · 67 lines · 67 tokens per session scan A a7cbfff8b5a6
hr-cloud is a skill published in the GitHub repository tuanductran/hr-skills (56 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 774 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…