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 ThomasMoreAI/legal-skills-open --skill recht-klage-momarcode1git clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/recht-klage-momarcode1)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/recht-klage-momarcode1"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/recht-klage-momarcode1/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/thomasmoreai/legal-skills-open/recht-klage-momarcode1"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/recht-klage-momarcode1.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.00044 | $0.02131 |
| Opus 5.5 | $0.00018 | $0.00852 |
| Sonnet 5.5 | $0.00009 | $0.00426 |
| Haiku 4.5 | $0.00004 | $0.00213 |
Grade A, and why
recht-klage-momarcode1 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 24d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/recht klage — Schriftsatz-Entwurf
When the user needs a legal filing drafted, follow these steps.
Step 1: Determine the Filing Type
Ask or infer what is needed:
| If user wants to... | Draft a... |
|---|---|
| Demand payment before suing | Mahnschreiben |
| Sue for money (undisputed) | Antrag auf Zahlungsbefehl (Mahnverfahren) |
| Sue (general) | Klage |
| Respond to a lawsuit | Klagebeantwortung |
| Appeal a judgment | Berufung (4 weeks from Zustellung!) |
| Object to a Zahlungsbefehl | Einspruch (4 weeks!) |
| Get emergency protection | Antrag auf einstweilige Verfügung |
| Apply in non-contentious matter | Antrag (AußStrG) |
Step 2: RIS Verification
Before proceeding with analysis, follow the RIS Verification Protocol (references/ris-protocol.md):
- Check RIS MCP availability
- For every § you cite in this analysis, verify current wording via RIS
- For case law references, retrieve via RIS Justiz
- Record verification status for the Quellenstatus block
- If RIS is unavailable, follow the fallback ladder and flag all affected citations
Step 3: Gather Required Information
For ANY filing you need:
- Full name + address of Kläger/Antragsteller (+ Geburtsdatum if natürliche Person)
- Full name + address of Beklagter/Antragsgegner
- The facts (chronological, complete)
- The evidence (what documents, witnesses exist)
- What the user wants the court to order (Begehren)
- Streitwert
Ask for anything missing. Be specific:
"Ich brauche die vollständige Adresse des Beklagten für den Schriftsatz."
Step 4: Draft the Filing
For a KLAGE, use this exact structure:
An das [Bezirksgericht/Landesgericht] [Ort]
Kläger: [Vollständiger Name]
[Straße, PLZ Ort]
geboren am [Datum]
[vertreten durch: RA Name, Adresse — if applicable]
Beklagter: [Vollständiger Name]
[Straße, PLZ Ort]
wegen: [Kurzbeschreibung — z.B. "Zahlung", "Gewährleistung", "Räumung"]
Streitwert: €[Betrag]
K L A G E
I. SACHVERHALT
1. [First fact — chronological. State only facts, no legal conclusions.]
Beweis: Beilage ./A [Beschreibung];
PV [= Parteienvernehmung des Klägers]
2. [Second fact]
Beweis: Beilage ./B; Zeuge [Name], [Adresse]
3. [Continue for all relevant facts]
Beweis: [evidence]
II. RECHTLICHE BEURTEILUNG
[Now apply law to facts. Structure:]
- State the applicable legal basis (§[x] [Gesetz])
- Subsume: "Der Beklagte hat [Tatbestandsmerkmal] verwirklicht, indem..."
- Cite OGH case law if helpful: "Der OGH hat in [GZ] entschieden, dass..."
- Address potential defenses preemptively if obvious
III. KLAGEBEGEHREN
Der Kläger stellt daher den
A N T R A G,
das Gericht möge den Beklagten schuldig erkennen,
1. dem Kläger den Betrag von €[Betrag] samt 4% Zinsen
seit [Datum — Fälligkeit oder Mahnung] binnen 14 Tagen
bei sonstiger Exekution zu bezahlen;
[ODER für B2B:]
... samt Zinsen in Höhe von 9,2 Prozentpunkten über dem
Basiszinssatz seit [Datum] ...
[ODER für Leistungsklage:]
[die konkrete Leistung zu erbringen / zu unterlassen / herauszugeben]
2. dem Kläger die Kosten dieses Rechtsstreits binnen 14 Tagen
bei sonstiger Exekution zu ersetzen.
[Ort], am [Datum]
____________________
[Name des Klägers / RA]
BEILAGENVERZEICHNIS:
./A [Beschreibung — z.B. "Kaufvertrag vom 01.03.2025"]
./B [Beschreibung — z.B. "E-Mail des Beklagten vom 15.04.2025"]
./C [Beschreibung]
What ships with it
2 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.
- 24d ago Changed · +3 lines 54dabb8ed1bd
- 26d ago First seen · 248 lines · 44 tokens per session scan A 5f5cb75cb252
recht-klage-momarcode1 is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 44 tokens to every session and 2,131 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…