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 map-australian-cyber-incident-obligations-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/map-australian-cyber-incident-obligations-l0cka)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/map-australian-cyber-incident-obligations-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/map-australian-cyber-incident-obligations-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/map-australian-cyber-incident-obligations-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/map-australian-cyber-incident-obligations-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.00128 | $0.00950 |
| Opus 5.5 | $0.00051 | $0.00380 |
| Sonnet 5.5 | $0.00026 | $0.00190 |
| Haiku 4.5 | $0.00013 | $0.00095 |
Grade A, and why
map-australian-cyber-incident-obligations-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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map Australian Cyber Incident Obligations
Build one independently verified row per entity and obligation. Read references/cyber-regime-registry.json before routing. The registry is a currency alarm and issue-spotting aid, not authority.
Workflow
- Record each entity and role, regulated sector, asset and data type, incident facts, availability impact, control weakness, outage, ransom demand, payment, awareness time, prior regulator notice and relevant contracts.
- Route each Commonwealth Act and instrument through
$check-commonwealth-legislation. Use$trace-commonwealth-legislative-changeacross an incident or remediation horizon that crosses an amendment or transition. - Apply the registry's supersession, trigger and clock prompts only after
verifying current primary text. A changed compilation, instrument inventory
or commencement point produces
CHECK REQUIRED, while urgent containment and already verified duties continue. - Preserve concurrent obligations. Do not collapse entities, awareness times, recipients or clocks into a single report or portal.
- Separate
Act,delegated legislative instrument or industry standard,enforceable prudential standard,regulator guidance,contract or insurance, andvoluntary reportin every output.
Mandatory overlap rules
- A 30-day NDB assessment period is not a 30-day notification deadline.
- Cyber Security Act Part 4 voluntary sharing does not discharge other duties, and limited-use provisions do not themselves create legal professional privilege.
- A single reporting portal is not a single-report safe harbour.
- CDR can require NDB treatment plus a separate ACSC report; do not fold CDR safeguards into the APPs.
- My Health Record section 75 can engage the Privacy Act section 26WD no-duplicate-notice rule; do not generalise it to other health incidents.
- Apply the CPS 234/CPS 230 interaction and earliest clock only after checking current APRA material. A ransomware payment and SOCI report can both apply.
- Telco DFV two-day notification can apply without NDB serious-harm eligibility.
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 · 86 lines · 128 tokens per session scan A 8c7b91c29c76
map-australian-cyber-incident-obligations-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 128 tokens to every session and 950 once invoked, about $0.0005 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…