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 The-AI-Directory-Company/agents-and-skills --skill employee-handbook-sectiongit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/employee-handbook-section)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/employee-handbook-section"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/employee-handbook-section/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/the-ai-directory-company/agents-and-skills/employee-handbook-section"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/employee-handbook-section.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01404 |
| Opus 5 | $0.00017 | $0.00702 |
| Sonnet 5 | $0.00007 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
employee-handbook-section 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 8d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Employee Handbook Section
Before you start
Gather the following from the user. Items 1-3 are required:
- What topic does this section cover? Name the specific policy area: PTO, remote work, code of conduct, expense reimbursement, performance reviews, etc.
- What is the company's stance? Every policy section needs a clear position. "We offer unlimited PTO" vs. "We offer 20 days per year" produces fundamentally different content.
- Who is the audience? All employees, managers only, specific departments, or contractors? This affects scope and tone.
- What jurisdiction(s) apply? Employment law varies by country, state, and city. Identify where employees are located.
- Does this replace an existing policy? If so, what is changing and why? This helps write the transition language.
- Who has final approval? Legal, HR leadership, executive team — identify the review chain before writing.
If the user says "write a PTO policy," push back: "What is the PTO structure — unlimited, accrual-based, or fixed allowance? What jurisdictions do you operate in?"
Important: Always include a disclaimer that the output requires legal review before publication. AI-generated policy language should never be published without review by qualified legal counsel familiar with applicable employment law.
Handbook section template
1. Section Header
# [Policy Name]
Effective date: [Date]
Last updated: [Date]
Applies to: [All employees / Managers / US employees / etc.]
Supersedes: [Previous policy name and date, or "N/A"]
Owner: [Department or role responsible for this policy]
Every section needs these metadata fields at the top. They prevent ambiguity about when the policy took effect and who it covers.
2. Purpose Statement
Write 2-3 sentences explaining:
- Why this policy exists (the business or legal reason)
- What it aims to achieve (the outcome for employees and the company)
Example: "This policy establishes clear guidelines for time-off requests to ensure fair and consistent treatment across all teams. It balances employee wellbeing with operational continuity."
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.
- 8d ago First seen · 132 lines · 34 tokens per session scan A fd6b20330991
employee-handbook-section is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,404 once invoked, about $0.0002 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
contract-redliner
Contract review, redlining, and negotiation support with clause analysis, risk identification, and markup templates. Use when reviewing contracts, identifying unfavorable terms, suggesting amendments, or preparing negotiation positions.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.
compliance-engineering
SOC2, HIPAA, GDPR, PCI-DSS, FedRAMP compliance implementation in code. Audit logging, data encryption, access controls, privacy by design, and regulatory requirement mapping. Use when implementing compliance controls, preparing for audits, or building privacy-compliant systems.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
cre-due-diligence
CRE Due Diligence analysis suite — 7 specialist skills for multifamily property analysis including rent roll validation, expense benchmarking, market study, physical inspection, environmental review, title review, and tenant credit assessment.
cre-legal
CRE Legal review suite — 6 specialist skills for PSA review, title & survey analysis, estoppel tracking, loan document review, insurance coordination, and transfer document preparation for multifamily acquisitions.