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 ciaransaunders/Skills-Public --skill employment-law-verifiergit clone --depth 1 https://github.com/ciaransaunders/Skills-PublicWrote 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/ciaransaunders/skills-public/employment-law-verifier)<a href="https://agentmods.dev/skills/ciaransaunders/skills-public/employment-law-verifier"><img src="https://agentmods.dev/badge/skills/ciaransaunders/skills-public/employment-law-verifier/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/ciaransaunders/skills-public/employment-law-verifier"><img src="https://agentmods.dev/badge/skills/ciaransaunders/skills-public/employment-law-verifier.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.00000 | $0.00837 |
| Opus 5 | $0.00000 | $0.00418 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
employment-law-verifier 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Employment Law Verifier
Expert verification of UK employment law documents to tribunal and appellate standards.
Use this skill to review, check, verify, analyse, or critique employment law documents — including ET/EAT skeleton arguments, written reasons, appeal grounds, witness statements, Schedule of Loss, legal correspondence, or drafts of submissions.
This skill applies rigorous verification, not legal advice. It flags errors and gaps rather than fixing them or telling the user what to do instead.
Before You Analyse Anything: Verify the Authorities
Employment law moves quickly and citations are easy to get wrong. Before analysing reasoning, check the key authorities cited:
- Case names and citations — confirm the case exists, is correctly cited, and says what the document claims
- Statutory provisions — confirm the section number and current wording
- Procedural rules — ET Rules 2013, EAT Rules 1993, current Practice Directions
- ACAS Codes — confirm the Code and paragraph actually say what is claimed
- Vento/injury to feelings bands — confirm you are using the current values (these update periodically)
Use web search to verify anything you are not certain about. Mark each authority as ✓ verified or ✗ unverified, and flag any discrepancy between what the document says and what you find.
This step matters because downstream reasoning built on a phantom case or a misquoted section is invalid regardless of how well-structured it looks.
Classify What You Find
There are two types of problem with different consequences:
Critical Error — breaks the logical chain. Examples: citing a case for a proposition it does not stand for, applying the wrong statutory test, missing a jurisdictional prerequisite, calculating a time limit incorrectly. When you hit one of these, explain it, flag that it invalidates the reasoning that depends on it, and then continue scanning the rest of the document for parts that stand independently.
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 · 71 lines · 0 tokens per session scan A 697719a12249
employment-law-verifier is a skill published in the GitHub repository ciaransaunders/Skills-Public (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 837 tokens. 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-31.
Other skills, from other repositories
governance
Manage the openEHR specification governance lifecycle — releases, change requests (CR/PR), and lifecycle states (DEVELOPMENT/TRIAL/STABLE…). This skill should be used when the user asks to create or tag a release, prepare a release branch, update the manifest for a release, submit or manage a CR/PR, promote a spec's…
counsel
Senior Contract Administrator & FIDIC / EPC contract specialist for oil, gas, refining, petrochemical, polymer, and upstream capital works. Use whenever the user mentions contract drafting, contract administration, FIDIC (Red Book / Yellow Book / Silver Book / Pink Book / Gold Book / Emerald Book / White Book), Pearl…
steward
Senior HSE, ESG, and Decarbonisation Specialist for oil & gas, refining, petrochemical, polymer, upstream, and energy projects. Use whenever the user mentions HSE management system (HSE-MS), ISO 14001 environmental management, ISO 45001 occupational health & safety, OHSAS 18001, ISO 50001 energy management, IOGP…
pentest-engagement-planner
Define legal scope, rules of engagement, and authorization artifacts for downstream pentest execution.
legal-firm-ops
Law firm operations and legal vertical workflows — client intake, conflict screening, time tracking, billing narratives, IOLTA, document review, contract risk flagging. Use when the user works at a law firm and asks about prospect qualification, retainer agreements, billable hour capture, trust accounting…
strm-mapping
Use when asked to map, crosswalk, align, compare, or gap-analyze any two cybersecurity frameworks, control catalogs, or regulatory requirements using NIST IR 8477 Set-Theory Relationship Mapping (STRM). Triggers on terms like "map controls", "crosswalk", "framework alignment", "gap analysis", or producing a STRM CSV…