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-claim-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-claim-momarcode1)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/recht-claim-momarcode1"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/recht-claim-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-claim-momarcode1"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/recht-claim-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.00051 | $0.02084 |
| Opus 5.5 | $0.00020 | $0.00834 |
| Sonnet 5.5 | $0.00010 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
recht-claim-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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/recht claim — Anspruchsprüfung
When the user describes a factual situation and wants to know their legal options, follow these steps.
Step 1: Gather the Facts
Read what the user has provided. You need:
- What happened? — Chronological sequence of events
- Who is involved? — Parties, their roles, consumer or business?
- When did it happen? — Dates are critical for Verjährung
- What does the user want? — Money, performance, rescission, injunction?
- What evidence exists? — Documents, witnesses, correspondence?
If any of these is missing, ask. Be specific:
"Wann genau ist das passiert? Das Datum ist wichtig für die Verjährungsprüfung."
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: Identify ALL Possible Claims
Go through this checklist systematically. Check every category — users often miss claims they didn't know they had.
A: Vertragliche Ansprüche (check first — these are strongest)
Ask yourself: Was there a contract (even oral)?
If yes, check each of these:
-
Erfüllung (§918 ABGB) — Can the user demand performance?
- Requirements: Valid contract + obligation due + no performance yet
- Check: Did user set a Nachfrist? (required per §918 unless entbehrlich)
-
Gewährleistung (§§922-933b ABGB) — Is there a Mangel (defect)?
- Requirements: Contract + Mangel at time of delivery + within Frist
- Check: Was it a Sachmangel or Rechtsmangel?
- Check: Did user assert it in time? (2 years movable, 5 years immovable per §933)
- Check B2B: Did user comply with §377 UGB Rügepflicht? (unverzüglich = within ~14 days)
- Remedies: First Verbesserung/Austausch → then Preisminderung/Wandlung (§932 ABGB Stufenmodell)
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 82904189c814
- 26d ago First seen · 206 lines · 51 tokens per session scan A 6b08ab595103
recht-claim-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 51 tokens to every session and 2,084 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…