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 legalithm-org/legalithm --skill plugingit clone --depth 1 https://github.com/legalithm-org/legalithmWrote 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/legalithm-org/legalithm/plugin)<a href="https://agentmods.dev/skills/legalithm-org/legalithm/plugin"><img src="https://agentmods.dev/badge/skills/legalithm-org/legalithm/plugin.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.00060 | $0.00860 |
| Opus 5 | $0.00030 | $0.00430 |
| Sonnet 5 | $0.00012 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
eu-ai-act-compliance 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- eu-ai-act-compliance — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EU AI Act compliance
The EU AI Act (Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744)
applies to AI systems placed on the EU market. This skill routes the work to the
legalithm MCP tools, which answer from a versioned rule corpus and cite an
Article for every claim.
When to reach for this
- A new AI feature is being added, or an existing one materially changes
- Someone asks "does the AI Act apply to us?" or "what do we have to do?"
- A customer questionnaire, tender, or investor asks about AI compliance
- A chatbot, generated content, deepfake, or emotion-recognition feature ships
How to work
Rule, before anything else: classify runs first. Every risk argument you
pass to another tool must come from a classify result in this conversation,
never from your own reading of the case. If you have not called classify yet,
you do not know the tier, and calling explain_obligation with a guessed tier
returns a confident list of the wrong duties. Guessing "high" and being right is
not the same as knowing.
1. Classify. Call classify with the role (provider or deployer), the
domain, a plain-sentence description of the use case, and the audience. It
returns a risk tier — unacceptable, high, limited, or minimal — with a cited
rationale and a confidence. The tier determines everything downstream.
2. Get the actual duties. Call explain_obligation with the role and the
tier as returned by classify. Each obligation comes back with its Article
citation, for example Article 9 risk management or Article 10 data governance.
Use those named duties. Do not paraphrase the Act from memory and do not write
fear copy.
3. Article 50 transparency. If the feature is user-facing AI, generate the
disclosure with generate_disclosure rather than hand-writing legal text.
Scenarios are chatbot (Art 50(1)), genai-content (Art 50(2)), deepfake
(Art 50(4)) and emotion (Art 50(3)); English and German are supported. Article
50 has applied since 2 August 2026, so this is a live obligation, not a
future one.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 67 lines · 60 tokens per session scan A 00b4b9234dd9
eu-ai-act-compliance is a skill published in the GitHub repository legalithm-org/legalithm (0 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 860 once invoked, about $0.0003 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…