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 msa-review-commercial-purchasegit 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/msa-review-commercial-purchase)<a href="https://agentmods.dev/skills/legalquants/lq-skills/msa-review-commercial-purchase"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/msa-review-commercial-purchase/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/msa-review-commercial-purchase"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/msa-review-commercial-purchase.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.00134 | $0.04546 |
| Opus 5.5 | $0.00054 | $0.01818 |
| Sonnet 5.5 | $0.00027 | $0.00909 |
| Haiku 4.5 | $0.00013 | $0.00455 |
Grade A, and why
msa-review-commercial-purchase 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.
This is a copy
100% identical to msa-review-commercial-purchase — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MSA Review — Commercial Purchase
Conduct a structured review of a commercial purchase Master Services Agreement from the user's stated perspective and produce a report that an in-house lawyer can act on without redoing the analysis. The output is a draft for human review, not a final word; treat it accordingly.
This skill is calibrated to commercial-grade purchase MSAs — agreements covering the procurement of physical goods, equipment, components, materials, or non-software services. It is not designed for: SaaS subscription agreements (use MSA Review — SaaS), professional-services-only agreements without physical deliverables (treat as a separate skill candidate; see DE-071 in the project PRD), construction agreements (significantly different structure and lien/payment-bond regime), real estate transactions, or government procurement (FAR-driven, distinct overlay).
When this skill applies
Apply when the user provides a Master Purchase Agreement, Master Supply Agreement, Master Goods Agreement, Master Procurement Agreement, or substantively similar commercial-procurement MSA and asks for review or redline guidance. The user's perspective — buyer or supplier — fundamentally changes the analysis; require it before proceeding if not supplied.
Do not apply this skill to:
- SaaS or software subscription agreements. Use MSA Review — SaaS.
- Construction agreements. Construction has a distinct regime (mechanic's liens, payment bonds, prevailing wage, retention) that this skill does not cover.
- Government procurement. FAR-driven federal procurement and many state procurements have substantial overlays; recommend external counsel familiar with the procurement regime.
- Real estate purchase or lease. Different instruments entirely.
- Pure professional-services agreements without physical deliverables. The structural shape differs enough from goods-purchase MSAs that a separate skill is appropriate (DE-071 candidate).
- Purchase Orders or Statements of Work alone. Those reference an MSA; review them in conjunction with the MSA (use the optional
order_forminput) or via a dedicated PO Review skill (DE-070 candidate). - NDAs or Quality Agreements accompanying the supply deal. Use NDA Review for confidentiality; quality agreements are typically reviewed in tandem with the MSA but are a distinct instrument warranting their own treatment.
What ships with it
7 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 · 257 lines · 134 tokens per session scan A 50d12045b7ac
msa-review-commercial-purchase is a skill published in the GitHub repository LegalQuants/lq-skills (64 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 134 tokens to every session and 4,546 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to msa-review-commercial-purchase, differing in 0 lines, and is treated as a copy.
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…