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 compute-procedural-deadlines-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/compute-procedural-deadlines-l0cka)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/compute-procedural-deadlines-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/compute-procedural-deadlines-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/compute-procedural-deadlines-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/compute-procedural-deadlines-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.00151 | $0.00828 |
| Opus 5.5 | $0.00060 | $0.00331 |
| Sonnet 5.5 | $0.00030 | $0.00166 |
| Haiku 4.5 | $0.00015 | $0.00083 |
Grade A, and why
compute-procedural-deadlines-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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compute Procedural Deadlines
Compute candidate deadlines with the bundled script and nothing else. A refusal from the script is a correct result: report the governing rule and the reason, and never fill the gap with model arithmetic.
Read the source and control method, use an approved profile per the deadline profile schema, and run compute_deadline.py against the computation-rule tables and holiday tables.
Workflow
- Fix the trigger and the forum.
- Record the forum, the procedural step, the lawyer-supplied trigger
date and what the trigger was (service, filing, judgment). A contested
or unknown trigger date is
NOT READY— never assume one.
- Record the forum, the procedural step, the lawyer-supplied trigger
date and what the trigger was (service, filing, judgment). A contested
or unknown trigger date is
- Locate the governing rule.
- Find the matching period rule in the forum's computation-rule table.
A step with no table entry is identify-only: name the governing rule
if known and route verification to
$verify-deadline-basis.
- Find the matching period rule in the forum's computation-rule table.
A step with no table entry is identify-only: name the governing rule
if known and route verification to
- Run the script.
- Call
scripts/compute_deadline.pywith the table id, period rule id and trigger date. Report the script's output faithfully:computedresults as candidate dates with the provisions applied and every warning;identify_onlyresults with the stated reason. - Never adjust, round or re-derive a date the script produced or refused. If holiday caveats flag registry-location uncertainty, surface them.
- Call
- Set the human decision gate.
- Name the confirmer who must confirm each candidate date and enter it in the diary system of record before any reliance.
Result contract
Lead with READY FOR HUMAN REVIEW, READY WITH QUALIFICATIONS, NOT READY
or OUTSIDE SCOPE.
Step: <forum; procedural step; governing rule citation>
Trigger: <lawyer-supplied trigger event and date; stated as assumption>
Script result: <computed candidate date and day | identify-only with reason>
Provisions applied: <citations from the script output; evidence states>
Warnings: <script warnings, holiday caveats, staging limits>
Human decision gate: <confirmer; diary entry pending confirmation>
Limitations: <candidate only; not a diary system; script-only arithmetic>
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.
- 22d ago First seen · 72 lines · 151 tokens per session scan A 54d62416a19b
compute-procedural-deadlines-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 151 tokens to every session and 828 once invoked, about $0.0006 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…