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 ThomasMoreAI/legal-skills-open --skill triage-legal-enquiry-l0ckagit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/triage-legal-enquiry-l0cka)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/triage-legal-enquiry-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/triage-legal-enquiry-l0cka/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/thomasmoreai/legal-skills-open/triage-legal-enquiry-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/triage-legal-enquiry-l0cka.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.00110 | $0.01170 |
| Opus 5.5 | $0.00044 | $0.00468 |
| Sonnet 5.5 | $0.00022 | $0.00234 |
| Haiku 4.5 | $0.00011 | $0.00117 |
Grade A, and why
triage-legal-enquiry-l0cka 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 22d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Legal Enquiry
Support authorised staff without replacing their judgment. Use the centre's approved profile as the controlling source and treat every outcome as provisional until a human confirms it. Keep version 0.1 staff-facing only.
Read references/triage-protocol.md before handling an enquiry. Use references/result-contract.md for the final record.
Preconditions
- Confirm that an authorised staff member, not a help-seeker acting alone, is operating the workflow.
- Require the centre's profile and a passing
--require-approvedvalidation. - Confirm that the AI environment is approved for the proposed data class.
- Remove names, contact details, addresses, dates of birth, document numbers and unnecessary narrative before using the model.
If any precondition fails, do not process further substantive facts. Return
URGENT HUMAN ESCALATION when facts already supplied indicate apparent urgent
risk; otherwise return HUMAN TRIAGE REQUIRED. Record the failed precondition
and the next authorised step.
Workflow
- Check immediate safety, liberty and time-critical risk using the configured escalation pathways. Escalate and stop ordinary triage when required.
- Record only whether the external conflict check is
passed,pending,uncertainornot started. Never request or reproduce party names. - Gather the minimum facts needed to identify the issue, jurisdiction, relevant dates, next event, requested help and access needs.
- Compare those facts with the profile. Cite the exact configured rule and distinguish facts, staff-supplied information, assumptions and unknowns.
- Select one permitted status and prepare the result contract. Require an authorised staff member to confirm, change or reject the proposed pathway.
Mandatory boundaries
- Do not give legal advice or state how the law applies to the person's facts.
- Do not infer identity, culture, disability, family violence, capacity, income, credibility, prospects or vulnerability.
- Do not describe a person as ineligible or a matter as lacking merit.
- Do not promise service acceptance, an appointment, confidentiality by a third party or referral availability.
- Do not write to CLASS, another client system or an external service.
What ships with it
4 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.
- 22d ago First seen · 124 lines · 110 tokens per session scan A a3e9c69ea77e
triage-legal-enquiry-l0cka is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 110 tokens to every session and 1,170 once invoked, about $0.0004 per session on Opus 5.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-10-06.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…