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 swiss-legal-source-authority-triage-enrique-g-zbindengit 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/swiss-legal-source-authority-triage-enrique-g-zbinden)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/swiss-legal-source-authority-triage-enrique-g-zbinden"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/swiss-legal-source-authority-triage-enrique-g-zbinden/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/swiss-legal-source-authority-triage-enrique-g-zbinden"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/swiss-legal-source-authority-triage-enrique-g-zbinden.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 119 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 203 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00106 | $0.03459 |
| Opus 5 | $0.00053 | $0.01729 |
| Sonnet 5 | $0.00021 | $0.00692 |
| Haiku 4.5 | $0.00011 | $0.00346 |
Grade A, and why
swiss-legal-source-authority-triage-enrique-g-zbinden 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 13d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swiss Legal Source & Authority Triage
Purpose
Use this skill to map the Swiss legal authority structure before producing a legal answer.
This skill does not provide Swiss legal advice. It helps an AI assistant identify the correct source layer, authority hierarchy, language/version checks, uncertainty flags, and human-review boundaries for Swiss legal research and legal-operations workflows.
Core thesis: for Swiss legal AI, route authority before generating an answer.
When to use this skill
Use this skill whenever:
- The user asks a question involving Swiss law, Switzerland, a Swiss party, Swiss assets, Swiss employment, Swiss contracts, Swiss courts, Swiss regulators, Swiss companies, Swiss data protection, Swiss financial regulation, Swiss IP, Swiss tax, Swiss criminal/public law, or Swiss cantonal/municipal law.
- The user asks whether a legal issue is federal, cantonal, communal, regulatory, contractual, professional, or mixed.
- The user asks for Swiss legal research sources, legal-source validation, or a legal source map.
- A contract, policy, memo, or compliance workflow claims to be governed by Swiss law.
- The answer could be affected by official-language versions, cantonal variation, regulator practice, pending reform, or register/legal-state evidence.
Safety and role limits
Do not present the output as legal advice. Use language such as:
This is a Swiss legal source and authority triage, not legal advice. It identifies likely source layers and review points. A qualified Swiss lawyer should review any concrete legal position, filing, advice to a client, or operational decision.
Escalate clearly when the issue involves:
- Litigation strategy, limitation periods, procedural deadlines, criminal exposure, regulatory authorisation, sanctions, employment termination, immigration, tax, financial-market authorisation, medical/health regulation, or court filings.
- Client-specific facts that materially affect the legal outcome.
- Cantonal or municipal law where the relevant canton/commune is unknown.
- Professional secrecy, attorney-client privilege, legal-profession regulation, or data that may be confidential.
- Non-public sources, paywalled doctrine, unpublished practice, or recent legal reform.
What ships with it
6 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.
- 13d ago First seen · 219 lines · 106 tokens per session scan A 008cfa9ba06c
swiss-legal-source-authority-triage-enrique-g-zbinden is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (72 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 3,459 once invoked, about $0.0005 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-30.
Other skills, from other repositories
pia-generator
Generate structured privacy impact assessments so Claude can organize project privacy risks, controls, and decision points into a review-ready report.
audit-scope-checklist
Generate a scoped IT audit program with controls mapped to roles and compliance frameworks. Use this skill for audit planning, control checklist generation, and auditprogram.json creation.
compliance-checker
Compare system configuration evidence against common control frameworks and produce a concise compliance assessment with gaps and remediation priorities.
compliance-controls-playbook
Guide Claude through a structured compliance audit workflow covering framework selection, evidence planning, control testing, exception handling, and reporting.
evidence-tracker
Manage audit evidence requests, collection progress, and status reporting so Claude can keep audits organized and identify overdue or blocked evidence items.
consent-checker
Review privacy policy or notice text against common privacy frameworks so Claude can explain coverage gaps, strengths, and compliance priorities.