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 LegalQuants/lq-skills --skill statutory-analysisgit clone --depth 1 https://github.com/LegalQuants/lq-skillsWrote 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/legalquants/lq-skills/statutory-analysis)<a href="https://agentmods.dev/skills/legalquants/lq-skills/statutory-analysis"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/statutory-analysis/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/legalquants/lq-skills/statutory-analysis"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/statutory-analysis.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.00133 | $0.05558 |
| Opus 5.5 | $0.00053 | $0.02223 |
| Sonnet 5.5 | $0.00027 | $0.01112 |
| Haiku 4.5 | $0.00013 | $0.00556 |
Grade A, and why
statutory-analysis 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 1mo 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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statutory Interpretation Guide (US Law)
A structured first-pass framework for reading US statutes, regulations, ordinances, and rules — federal, state (all 50 states + DC + US territories), and local (county / municipal). Claude organises the analysis; a named attorney owns every legal conclusion.
This skill does not handle non-US law (EU, UK, Canada, foreign jurisdictions, international treaties). If the user's matter touches foreign law, halt and route to counsel qualified in that jurisdiction.
Audience
Junior associates, compliance analysts, and paralegals conducting first-pass statutory review. All outputs require attorney review before any client-facing, regulatory, or transactional use. This skill is not for self-represented users seeking legal advice — the firewall between "structuring analysis" and "giving advice" exists because misreading statutory text has real consequences for real people, and a named attorney is the only person qualified to bear that risk.
Work Shape
Accretive Judgment. Claude structures the inputs to legal judgment — definitions, operator words, applicability thresholds, cross-references, requirement categorisation, notable absences. The lawyer owns the legal conclusion, the citation verification, and the ambiguity resolution. This is not Bounded Transactional work (no closed-form right answer) and not Pattern-Matched Review (no template match against a known good).
When to Use This Skill
Use when the user asks for first-pass structuring of:
- How to read and interpret a specific statute, regulation, or rule
- Statutory interpretation methods and canons of construction
- Legislative intent extraction
- Requirements extraction from statutory text
- Applicability / threshold analysis
- Cross-jurisdictional compliance scoping
Out of Scope
This skill does not perform:
- Non-US law of any kind — EU regulations (GDPR, DSA, AI Act), UK statutes, Canadian / Australian / Singaporean / other foreign law, or international treaties. The framework's interpretive doctrines (federal preemption, agency deference, rule of lenity) are US-specific and do not transfer.
- Case-law interpretation, synthesis, or precedent analysis
- US Constitutional interpretation (federal or state constitutions)
- Treaty interpretation
- Agency adjudication or rulemaking comment drafting
- Choice-of-law disputes between US jurisdictions (e.g., which state's law governs a multi-state transaction)
- Drafting statutory, regulatory, or ordinance language
- Lobbying or legislative-strategy analysis
- Final legal opinions, client memos, briefs, or filings
What ships with it
5 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.
- 1mo ago First seen · 468 lines · 133 tokens per session scan A 94f17e5e6499
statutory-analysis is a skill published in the GitHub repository LegalQuants/lq-skills (64 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 133 tokens to every session and 5,558 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
fto-triage
Freedom-to-operate triage — a structured first look at potentially blocking patents, not an FTO opinion. Use when a product, process, or feature is being evaluated for blocking patents, when asked whether anything stops a launch, or to build a claim-chart first pass against the most plausible patents before patent…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
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.
terms-of-service
Draft terms of service and a companion privacy notice matched to the product's form and feature modules, not legal advice, delivered as a Word document.
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.
ai-risk-management
Apply the NIST AI Risk Management Framework (AI RMF 1.0) and adjacent guidance to AI / ML systems — model lifecycle governance, fairness and bias evaluation, robustness, transparency, accountability, third-party model risk, monitoring for drift, and AI incident response. Broader than prompt-injection (which is the…