format-aglc4-citations-l0cka

format-aglc4-citations-l0cka is a skill for Codex from ThomasMoreAI/legal-skills-open. It costs 116 tokens per session (1,051 once invoked), scanned A, original, Apache-2.0.

A formatting tool for Australian Guide to Legal Citation, fourth edition (AGLC4), the standard style used for many Australian legal citations and bibliographies. It handles sources such as cases, legislation, books, articles, and treaties.

In plain words
What is it for?
Use it to draft, convert, review, or correct Australian legal citations, footnotes, pinpoints, and bibliographies.
Why use it?
It helps make footnotes and bibliographies consistent without inventing missing source details. It can also identify unresolved information that must be supplied or checked.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to draft, convert, review, or correct Australian legal citations, footnotes, pinpoints, and bibliographies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thomasmoreai/legal-skills-open/format-aglc4-citations-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 format-aglc4-citations-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 format-aglc4-citations-l0cka

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/format-aglc4-citations-l0cka"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/format-aglc4-citations-l0cka.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,051 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.00116 $0.01051
Opus 5.5 $0.00046 $0.00420
Sonnet 5.5 $0.00023 $0.00210
Haiku 4.5 $0.00012 $0.00105

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

Security

Grade A, and why

format-aglc4-citations-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/general/skills/format-aglc4-citations-l0cka/SKILL.md · 64 lines

How it starts

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

Apply AGLC4 to every citation. Preserve the source's substantive details; change only citation form unless the user asks for source verification or correction.

Workflow

  1. Identify each source type before formatting it. Do not format from a URL, database label, or incomplete search result when the source itself is available.
  2. Read references/general-rules.md for every task. Then read the topic reference that covers the source:
  3. Collect and verify every required field. Mark a missing field as unresolved; never invent an author, date, court, report series, document number, pinpoint, URL, or access detail.
  4. Build the first citation in full. Add the most precise useful pinpoint. Use an authorised report before an unauthorised report or medium-neutral citation when AGLC4 requires that preference.
  5. Apply Ibid, (n X), a short title, or at only after checking the citation sequence. Renumber cross-references after footnotes move.
  6. If the document requires a bibliography or References section, include every source relied on and transform footnote citations under AGLC4 rule 1.13. Read references/citation-templates-and-audit.md.
  7. Run a final audit for source identity, element order, italics, quotation marks, brackets, commas, pinpoints, subsequent references, URLs, bibliography ordering, and closing punctuation.

Read the full file on GitHub · 64 lines

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 · 64 lines · 116 tokens per session scan A 271d9dac2b3e

Subscribe to this mod's changes

format-aglc4-citations-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 116 tokens to every session and 1,051 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-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