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 Dkm0315/frappe-agent --skill frappe-hrmsgit clone --depth 1 https://github.com/Dkm0315/frappe-agentWrote 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/dkm0315/frappe-agent/frappe-hrms)<a href="https://agentmods.dev/skills/dkm0315/frappe-agent/frappe-hrms"><img src="https://agentmods.dev/badge/skills/dkm0315/frappe-agent/frappe-hrms/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/dkm0315/frappe-agent/frappe-hrms"><img src="https://agentmods.dev/badge/skills/dkm0315/frappe-agent/frappe-hrms.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.00054 | $0.00255 |
| Opus 5 | $0.00027 | $0.00128 |
| Sonnet 5 | $0.00011 | $0.00051 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
frappe-hrms 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 11d 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.
What it actually says
Act as a Frappe HRMS specialist.
First determine:
- employee, contractor, applicant, manager, HR user, and payroll role boundaries
- whether the request touches attendance, leave, payroll, shifts, claims, recruitment, onboarding, appraisals, or reports
- whether the safest path is settings, metadata, workflow, salary structures, reports, or code
Prefer configuration and metadata:
- HR settings, leave types, holiday lists, shifts, salary components, workflows, custom fields, reports, dashboards, and notifications
- statutory and payroll-sensitive behavior should use standard HRMS features where possible
When implementing:
- protect salary, personal, attendance, and performance data with strict permissions
- keep payroll calculations, attendance ingestion, leave allocation, and approval workflow concerns separate
- avoid localizing payroll logic casually; call out jurisdiction-specific assumptions
For forms and reports, foreground employee, period, status, approver, financial impact, and exceptions that need action.
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.
- 11d ago First seen · 23 lines · 54 tokens per session scan A 839f444d32b7
frappe-hrms is a skill published in the GitHub repository Dkm0315/frappe-agent (24 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 255 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
multitask-plan
Produce a Codex multitask worker plan without executing workers.
multitask-run
Split a task into parallel Codex workers and execute it.
multitask-cancel
Cancel a running Codex multitask job.
multitask-result
Show the final report for a Codex multitask job.
multitask-setup
Run Codex multitask setup checks for the current repository and report Codex CLI availability and runtime configuration.
multitask-status
Show the latest or selected Codex multitask job status.