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-mcp --skill folio-classify-eventgit clone --depth 1 https://github.com/alea-institute/folio-mcpWrote 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-mcp/folio-classify-event)<a href="https://agentmods.dev/skills/alea-institute/folio-mcp/folio-classify-event"><img src="https://agentmods.dev/badge/skills/alea-institute/folio-mcp/folio-classify-event/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-mcp/folio-classify-event"><img src="https://agentmods.dev/badge/skills/alea-institute/folio-mcp/folio-classify-event.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.00427 |
| Opus 5 | $0.00043 | $0.00214 |
| Sonnet 5 | $0.00017 | $0.00085 |
| Haiku 4.5 | $0.00009 | $0.00043 |
Grade A, and why
folio-classify-event 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 10d 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.
What it actually says
Classify a Legal Event with FOLIO
Classify a legal event against the FOLIO ontology's events taxonomy branch.
Workflow
Given a description of a legal event, follow these steps:
-
Search for matches: Use
folio:search_conceptswith the event description or key terms to find candidate event types in FOLIO. -
Browse the events taxonomy: Use
folio:get_taxonomy_branch("events")to review all 14 top-level event categories (e.g., Dispute Events, Transaction Events, Bankruptcy and Restructuring Events, Regulatory Events, Employment Events, etc.). -
Drill into the best category: Use
folio:get_children(iri)on the most promising category to find the specific event 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 event type
- Parent Category: The parent event category in the taxonomy hierarchy
- Confidence: high / medium / low
- Reasoning: Brief explanation of why this classification was chosen
If the event spans multiple categories (e.g., a bankruptcy-related dispute hearing), list all applicable types with primary/secondary relevance.
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.
- 10d ago First seen · 34 lines · 86 tokens per session scan A 3344ec25cd30
folio-classify-event is a skill published in the GitHub repository alea-institute/folio-mcp (5 stars, last pushed 5mo ago), licensed MIT. It adds 86 tokens to every session and 427 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.
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.
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…
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…