folio-identify-legal-authority

folio-identify-legal-authority is a skill for Claude Code, Codex from alea-institute/folio-mcp. It costs 97 tokens per session (443 once invoked), scanned A, original, MIT.

A classifier for identifying what kind of legal source a citation or rule comes from, such as a statute, regulation, court case, treaty, or constitution. It uses the FOLIO legal-authority taxonomy.

In plain words
What is it for?
Use it to classify a legal citation or source of law and return its FOLIO category, subtype, definition, parent category, and identifier.
Why use it?
It removes the need to classify legal sources manually or rely on inconsistent labels. It also provides the official category, definition, identifier, and related references.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to classify a legal citation or source of law and return its FOLIO category, subtype, definition, parent category, and identifier.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alea-institute/folio-mcp/folio-identify-legal-authority
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 alea-institute/folio-mcp --skill folio-identify-legal-authority
Clone the repo
git clone --depth 1 https://github.com/alea-institute/folio-mcp

Made for: Claude Code, 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 folio-identify-legal-authority

README.md
[![agentmods](https://agentmods.dev/badge/skills/alea-institute/folio-mcp/folio-identify-legal-authority/github.svg)](https://agentmods.dev/skills/alea-institute/folio-mcp/folio-identify-legal-authority)
Your own site
<a href="https://agentmods.dev/skills/alea-institute/folio-mcp/folio-identify-legal-authority"><img src="https://agentmods.dev/badge/skills/alea-institute/folio-mcp/folio-identify-legal-authority/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 folio-identify-legal-authority

Your own site · 80×15
<a href="https://agentmods.dev/skills/alea-institute/folio-mcp/folio-identify-legal-authority"><img src="https://agentmods.dev/badge/skills/alea-institute/folio-mcp/folio-identify-legal-authority.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 443 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.00097 $0.00443
Opus 5.5 $0.00039 $0.00177
Sonnet 5.5 $0.00019 $0.00089
Haiku 4.5 $0.00010 $0.00044

Measured 2mo ago against content hash 0777d0e730ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

folio-identify-legal-authority 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 2mo 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.

skills/folio-identify-legal-authority/SKILL.md · 34 lines

What it actually says

Identify the type of legal authority using the FOLIO ontology's legal_authorities taxonomy branch.

Workflow

Given a legal citation, rule, regulation, or source of law, follow these steps:

  1. Search for matches: Use folio:search_concepts with the authority name or type to find candidate authority types in FOLIO.

  2. Browse the authority taxonomy: Use folio:get_taxonomy_branch("legal_authorities") to review all 14 top-level authority types (e.g., Statutes, Regulations, Caselaw, Treaties, Executive Orders, Constitutions, etc.).

  3. Drill into the best category: Use folio:get_children(iri) on the most promising category to find the specific authority subtype.

  4. Get full details: Use folio:get_concept(iri) on the best match to retrieve the complete definition, translations, identifiers, and cross-references.

Output Format

Return the classification as:

  • FOLIO Label: The official FOLIO concept name
  • FOLIO IRI: The concept's unique identifier (e.g., https://folio.openlegalstandard.org/...)
  • Definition: The FOLIO definition of this authority type
  • Parent Category: The parent category in the taxonomy hierarchy
  • Confidence: high / medium / low
  • Reasoning: Brief explanation of why this classification was chosen

If the authority could be classified under multiple types (e.g., an administrative regulation with statutory authority), note both classifications.

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. 2mo ago First seen · 34 lines · 97 tokens per session scan A 0777d0e730ff

Subscribe to this mod's changes

folio-identify-legal-authority is a skill published in the GitHub repository alea-institute/folio-mcp (5 stars, last pushed 7mo ago), licensed MIT. It adds 97 tokens to every session and 443 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-08-31.

Related

folio-identify-legal-authority compared with skills from other repositories

folio-identify-legal-authority next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
folio-identify-legal-authorityalea-institute/folio-mcpSkill57mo agoMITA97Claude Code, Codex
fto-triageanthropics/claude-for-legalSkill9.9k3d agoApache-2.0A81Claude Code
legal-holdanthropics/claude-for-legalSkill9.9k3d agoApache-2.0A68Claude Code
specification-writingwanshuiyin/Auto-claude-code-research-in-sleepSkill19k3d agoMITA49Claude Code
terms-of-servicegenspark-ai/genofficeSkill12kyesterdayApache-2.0A32Claude Code, Codex
x-scorecardx-cmd/x-cmdSkill4.7k7d agoApache-2.0A57Claude Code, Codex
gesellschaftsrechtliche-satzungen-agbKlotzkette/claude-fuer-deutsches-rechtSkill1.8kyesterdayApache-2.0A69Claude Code