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 folio-classify-documentgit 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-classify-document)<a href="https://agentmods.dev/skills/alea-institute/folio-claude-plugin/folio-classify-document"><img src="https://agentmods.dev/badge/skills/alea-institute/folio-claude-plugin/folio-classify-document.svg" alt="Measured on agentmods" 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.00099 | $0.00430 |
| Opus 5 | $0.00049 | $0.00215 |
| Sonnet 5 | $0.00020 | $0.00086 |
| Haiku 4.5 | $0.00010 | $0.00043 |
Grade A, and why
folio-classify-document 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 7d 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.
This is a copy
100% identical to folio-classify-document — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Classify a Legal Document with FOLIO
Classify a legal document against the FOLIO ontology's document_artifacts taxonomy branch.
Workflow
Given a document name or description, follow these steps:
-
Search for matches: Use
folio:search_conceptswith the document name or key terms to find candidate document types in FOLIO. -
Browse the document taxonomy: If no strong match is found, use
folio:get_taxonomy_branch("document_artifacts")to see the top-level document categories (e.g., Contracts, Court Documents, Legislative Documents, etc.). -
Drill into the best category: Use
folio:get_children(iri)on the most promising top-level category to find the specific document type. -
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 document type
- Parent Category: The parent concept in the taxonomy hierarchy
- Confidence: high / medium / low
- Reasoning: Brief explanation of why this classification was chosen
If multiple classifications could apply, list the primary match first, then alternatives with their confidence levels.
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.
- 7d ago First seen · 34 lines · 99 tokens per session scan A e5a4d39f8c04
folio-classify-document is a skill published in the GitHub repository alea-institute/folio-claude-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 99 tokens to every session and 430 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to folio-classify-document, differing in 0 lines, and is treated as a copy.
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…