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-strategy-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-strategy-momarcode1)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/recht-strategy-momarcode1"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/recht-strategy-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-strategy-momarcode1"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/recht-strategy-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.00037 | $0.02101 |
| Opus 5.5 | $0.00015 | $0.00840 |
| Sonnet 5.5 | $0.00007 | $0.00420 |
| Haiku 4.5 | $0.00004 | $0.00210 |
Grade A, and why
recht-strategy-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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/recht strategy — Prozessstrategie
When the user has a dispute and wants to know how to proceed, follow these steps.
Step 1: Collect Context
You need the outputs from /recht claim and /recht evidence. If those haven't been run yet, do their analysis first (at least mentally — you don't need to output them separately).
Confirm you know:
- The viable claims (from claim analysis)
- The evidence strength (from evidence evaluation)
- The Streitwert
- The user's goal (money? performance? injunction? vindication?)
- Timeline constraints (urgent? Verjährung approaching?)
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
Search RIS Justiz for 3-5 relevant OGH decisions per key legal issue. Present using format from references/ogh-case-presentation.md.
Step 3: Determine the Court
Sachliche Zuständigkeit — which level of court?
Check in this order:
-
Is there a special court?
- Arbeitsrecht → ASG (Arbeits- und Sozialgericht) per ASGG
- Handelsrecht → Handelsgericht / Handelssenat per §51 JN
- Mietrecht (MRG, WEG) → BG regardless of Streitwert per §49 Abs 2 Z 5 JN
- Familienrecht → BG per §49 Abs 2 JN
-
If no special court: Streitwert decides
- ≤ €15.000 → Bezirksgericht (BG)
-
€15.000 → Landesgericht (LG) per §49 JN
Örtliche Zuständigkeit — which location?
Check in this order:
- Is there a valid Gerichtsstandsvereinbarung (§104 JN)?
- In B2C: Only valid per §14 KSchG if at user's Wohnsitz
- Is there a besonderer Gerichtsstand?
- Erfüllungsort (§88 JN), Schadenort (§92a JN), Liegenschaft (§81 JN)
- Default: Wohnsitz/Sitz des Beklagten (§66 JN)
What ships with it
3 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 · +5 lines 39f44574ea23
- 26d ago First seen · 228 lines · 37 tokens per session scan A c45e8c23981a
recht-strategy-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 37 tokens to every session and 2,101 once invoked, about $0.0001 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…