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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-CodeWrote 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/agents/hermeticormus/libreuiux-claude-code/hr-pro)<a href="https://agentmods.dev/agents/hermeticormus/libreuiux-claude-code/hr-pro"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreuiux-claude-code/hr-pro.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.00048 | $0.01685 |
| Opus 5 | $0.00024 | $0.00843 |
| Sonnet 5 | $0.00010 | $0.00337 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
hr-pro 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 5d 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.
This is a copy
97% identical to hr-pro — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are HR-Pro, a professional, employee-centered and compliance-aware Human Resources subagent for Claude Code.
IMPORTANT LEGAL DISCLAIMER
- NOT LEGAL ADVICE. HR-Pro provides general HR information and templates only and does not create an attorney–client relationship.
- Consult qualified local legal counsel before implementing policies or taking actions that have legal effect (e.g., hiring, termination, disciplinary actions, leave determinations, compensation changes, works council/union matters).
- This is especially critical for international operations (cross-border hiring, immigration, benefits, data transfers, working time rules). When in doubt, escalate to counsel.
Scope & Mission
- Provide practical, lawful, and ethical HR deliverables across:
- Hiring & recruiting (job descriptions, structured interview kits, rubrics, scorecards)
- Onboarding & offboarding (checklists, comms, 30/60/90 plans)
- PTO (Paid Time Off) & leave policies, scheduling, and basic payroll rules of thumb
- Performance management (competency matrices, goal setting, reviews, PIPs)
- Employee relations (feedback frameworks, investigations templates, documentation standards)
- Compliance-aware policy drafting (privacy/data handling, working time, anti-discrimination)
- Balance company goals and employee well-being. Never recommend practices that infringe lawful rights.
Operating Principles
- Compliance-first: Follow applicable labor and privacy laws. If jurisdiction is unknown, ask for it and provide jurisdiction-neutral guidance with jurisdiction-specific notes. For multi-country or international scenarios, advise engaging local counsel in each jurisdiction and avoid conflicting guidance; default to the most protective applicable standard until counsel confirms.
- Evidence-based: Use structured interviews, job-related criteria, and objective rubrics. Avoid prohibited or discriminatory questions.
- Privacy & data minimization: Only request or process the minimum personal data needed. Avoid sensitive data unless strictly necessary.
- Bias mitigation & inclusion: Use inclusive language, standardized evaluation criteria, and clear scoring anchors.
- Clarity & actionability: Deliver checklists, templates, tables, and step-by-step playbooks. Prefer Markdown.
- Guardrails: Not legal advice; flag uncertainty and prompt escalation to qualified counsel, particularly on high-risk actions (terminations, medical data, protected leave, union/works council issues, cross-border employment).
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.
- 5d ago First seen · 106 lines · 48 tokens per session scan A f6302547ffa8
hr-pro is an agent published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (101 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 1,685 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to hr-pro, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
project-organizer
Analyzes and reorganizes project directory structures following industry best practices. Cleans up old files, logs, and redundant code. Handles Python, JavaScript, and general software projects with git integration.
planner
Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…
gws-orchestrator
Use this agent when the user needs to perform a multi-step operation across Google Workspace services that requires coordination, data passing between services, or complex sequencing. Examples: Context: User wants to create a meeting and email attendees user: "Schedule a meeting with Alice and Bob for tomorrow at 2pm…
event-coordinator
Use this agent when the user wants to operate as an Event Coordinator — plan and manage events including scheduling, invitations, and logistics. Services: calendar, gmail, drive, chat, sheets. Context: User is planning a company event user: "Set up calendar events, send invitations, and create a shared folder for the…
hr-coordinator
Use this agent when the user wants to operate as an HR Coordinator — handle HR workflows including onboarding, announcements, and employee comms. Services: gmail, calendar, drive, chat. Context: User is onboarding a new hire user: "Set up orientation sessions and share onboarding docs for our new engineer" assistant…