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 alea-institute/folio-claude-plugin --skill foliogit clone --depth 1 https://github.com/alea-institute/folio-claude-pluginWrote 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/alea-institute/folio-claude-plugin/folio)<a href="https://agentmods.dev/skills/alea-institute/folio-claude-plugin/folio"><img src="https://agentmods.dev/badge/skills/alea-institute/folio-claude-plugin/folio/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/alea-institute/folio-claude-plugin/folio"><img src="https://agentmods.dev/badge/skills/alea-institute/folio-claude-plugin/folio.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.00086 | $0.00966 |
| Opus 5 | $0.00043 | $0.00483 |
| Sonnet 5 | $0.00017 | $0.00193 |
| Haiku 4.5 | $0.00009 | $0.00097 |
Grade A, and why
folio 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FOLIO Legal Ontology Skill
When to Use
Use the FOLIO MCP tools when you need to:
- Classify legal concepts: Find the correct ontology term for a legal concept
- Identify document types: Look up legal document classifications (contracts, filings, opinions)
- Find areas of law: Determine which legal practice area applies
- Map entity types: Identify types of legal entities (corporations, trusts, partnerships)
- Explore relationships: Find how legal concepts relate to each other
- Export definitions: Get formal definitions in markdown, JSON-LD, or OWL XML
How to Search
Follow this workflow:
- Search by name: Start with
folio:search_concepts(query)to find concepts by label - Refine by definition: If name search is too broad, use
folio:search_definitions(query) - Advanced query: Use
folio:query_concepts(label, definition, branch, parent)for composable filters - Query properties: Use
folio:query_properties(label, definition, domain, range)to find relationships - Browse branches: Use
folio:list_branches()thenfolio:get_taxonomy_branch(branch_name)to explore a category - Navigate hierarchy: Use
folio:get_children(iri)andfolio:get_parents(iri)to explore up/down the taxonomy
Classification Workflows
Three specialized classification workflows are available as slash commands. Suggest these to users when they need structured FOLIO classification:
| Slash Command | Use When | Key Branches |
|---|---|---|
/folio:classify-document |
Classifying a legal document type | document_artifacts |
/folio:identify-area-of-law |
Identifying areas of law for a situation | areas_of_law |
/folio:classify-entity |
Classifying a legal entity, role, or org | actors_players, legal_entities |
Each workflow searches, browses the relevant taxonomy branch, navigates to the best match, and returns: FOLIO Label, IRI, Definition, Confidence, and Reasoning.
Branch Reference
| Branch Key | Description |
|---|---|
actors_players |
Parties, roles, participants |
areas_of_law |
Practice areas, specializations |
asset_types |
Property, IP, financial assets |
communication_modalities |
Communication channels |
currencies |
Monetary currencies |
data_formats |
Data and file formats |
document_artifacts |
Legal documents, contracts |
engagement_terms |
Fee arrangements, engagement terms |
events |
Legal events, milestones |
forum_venues |
Courts, tribunals, venues |
governmental_bodies |
Government agencies |
industries |
Industry sectors |
languages |
Natural languages |
folio_types |
Internal FOLIO types |
legal_authorities |
Statutes, regulations, case law |
legal_entities |
Corporations, LLCs, trusts |
locations |
Geographic locations |
matter_narratives |
Matter descriptions |
matter_narrative_formats |
Narrative formats |
objectives |
Legal objectives |
services |
Legal services |
standards_compatibilities |
Standards mappings |
statuses |
Status values |
system_identifiers |
External identifiers |
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.
- 9d ago First seen · 88 lines · 0 tokens per session scan A 542ee49ede8f
folio is a skill published in the GitHub repository alea-institute/folio-claude-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 86 tokens to every session and 966 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…