verify-deadline-basis-l0cka

verify-deadline-basis-l0cka is a skill for Codex from ThomasMoreAI/legal-skills-open. It costs 144 tokens per session (1,047 once invoked), scanned A, original, Apache-2.0.

A verification process for the legal rules and public-holiday tables used to calculate Australian litigation deadlines. It checks those inputs against official legislation and government sources before they are used.

In plain words
What is it for?
Use it to verify limitation rules, court and tribunal rules, interpretation rules, and public-holiday information needed by deadline calculations.
Why use it?
It reduces the risk of calculating a deadline from an outdated or unsupported rule. Unverified entries remain blocked rather than being silently used.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

Good fit Use it to verify limitation rules, court and tribunal rules, interpretation rules, and public-holiday information needed by deadline calculations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thomasmoreai/legal-skills-open/verify-deadline-basis-l0cka
Install

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.

Any agent
npx skills add ThomasMoreAI/legal-skills-open --skill verify-deadline-basis-l0cka
Clone the repo
git clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-open

Made for: Codex.

Wrote 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.

agentmods badge for verify-deadline-basis-l0cka

README.md
[![agentmods](https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/verify-deadline-basis-l0cka/github.svg)](https://agentmods.dev/skills/thomasmoreai/legal-skills-open/verify-deadline-basis-l0cka)
Your own site
<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/verify-deadline-basis-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/verify-deadline-basis-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.

agentmods 80×15 button for verify-deadline-basis-l0cka

Your own site · 80×15
<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/verify-deadline-basis-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/verify-deadline-basis-l0cka.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 144 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,047 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00144 $0.01047
Opus 5.5 $0.00058 $0.00419
Sonnet 5.5 $0.00029 $0.00209
Haiku 4.5 $0.00014 $0.00105

Measured 19d ago against content hash 410edc0a98a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify-deadline-basis-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 19d 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.

au/litigation/skills/verify-deadline-basis-l0cka/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verify Deadline Basis

Verify the tables computation depends on, entry by entry, against the official publishers, and record the evidence. An entry stays pending-verification — and the script keeps refusing to compute from it — until this workflow confirms it.

Read the source and control method and verify the computation-rule tables and holiday tables.

Workflow

  1. Fix the verification scope.
    • Record which tables and entries the matter relies on, the assessment date and the previous fingerprint if one exists.
  2. Verify each entry against its publisher.
    • For Acts (Interpretation Acts, Limitation Acts, tribunal Acts), route to the Australian Legal Research checkers ($check-commonwealth-legislation, $check-nsw-legislation, $check-victoria-legislation or the applicable sibling) and record the result.
    • For court rules and procedural instruments, check the official legislation publisher for the jurisdiction directly: confirm the provision exists, its current text supports the table's summary and period, and record the version identifier and checked date. Never bypass a publisher's bot protections; an unreachable source leaves the entry pending-verification.
    • For holiday tables, check the official government publication, confirm the dates and uncertain windows, and record the page's last-updated signal.
  3. Record the outcome.
    • For each entry: VERIFIED, VERIFIED WITH QUALIFICATIONS or NOT VERIFIED, with source URL, version identifier and checked date. Compute a fingerprint over the verified table content and compare with the previous fingerprint; report every change as a change, never silently.
    • Present table updates as drafts for the practice to apply and store — the workflow itself marks nothing verified without the human applying the update.
  4. Set the human decision gate.
    • Name who applies the table updates and who decides reliance where an entry stays NOT VERIFIED.

Read the full file on GitHub · 100 lines

Files

What ships with it

2 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.

Changes

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.

  1. 19d ago First seen · 100 lines · 144 tokens per session scan A 410edc0a98a3

Subscribe to this mod's changes

verify-deadline-basis-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 144 tokens to every session and 1,047 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-09.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens