contract-summary

contract-summary is a command for Claude Code from alexclowe/awesome-claude-cowork-plugins. It costs 15 tokens per session (1,514 once invoked), scanned A, original, MIT.

A legal documentation command that creates a structured summary of a contract. It highlights the agreement’s main terms, duties, risks, unusual provisions, parties, and important dates for an attorney’s review.

In plain words
What is it for?
Use it to summarise contracts, list each party’s obligations, describe duration and other key terms, assess overall risk, and identify unusual or urgent provisions.
Why use it?
It helps turn a lengthy or unfamiliar agreement into a clear review document and draws attention to concerns that may need discussion before signing.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the attorney plugin — 4 skills, 8 commands shipped together

Good fit Use it to summarise contracts, list each party’s obligations, describe duration and other key terms, assess overall risk, and identify unusual or urgent provisions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alexclowe/awesome-claude-cowork-plugins/contract-summary
Install

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.

Clone the repo
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-plugins

Made for: Claude Code.

Or install attorney, the plugin that ships this one along with the rest of its 4 skills, 8 commands.

Wrote 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.

agentmods badge for contract-summary

README.md
[![agentmods](https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/contract-summary/github.svg)](https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/contract-summary)
Your own site
<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/contract-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/contract-summary/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.

agentmods 80×15 button for contract-summary

Your own site · 80×15
<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/contract-summary"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/contract-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,514 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.01514
Opus 5 $0.00008 $0.00757
Sonnet 5 $0.00003 $0.00303
Haiku 4.5 $0.00002 $0.00151

Measured 12d ago against content hash b057bc7624f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

contract-summary 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 12d 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.

attorney/commands/contract-summary.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a legal documentation assistant helping a licensed attorney draft contract review summaries.

The user will provide details about a contract — this may include the contract type, parties, key terms, or specific concerns. Your job is to generate a structured contract review summary that highlights key terms, obligations, risks, and unusual provisions, ready for the attorney's review and client communication.

Contract review summary format

CONFIDENTIAL — ATTORNEY-CLIENT PRIVILEGED

CONTRACT REVIEW SUMMARY

Date: [Date]
Attorney: [To be signed]
File No.: [To be assigned]
Client: [Client name — attorney to complete]

Document Reviewed: [Contract title / type]
Parties: [Party A] ("______") and [Party B] ("______")
Date of Agreement: [As stated or "undated"]
Effective Date: [If different from date of agreement]

─────────────────────────────────────────────

EXECUTIVE SUMMARY:
[2-3 sentence high-level summary of what this contract does, who it benefits,
and the overall risk level for the client (Low / Moderate / High). Flag any
immediate concerns that require attention before execution.]

─────────────────────────────────────────────

KEY TERMS:

Term / Duration:
- Initial term: [Duration]
- Renewal: [Auto-renewal / manual renewal / notice requirements]
- Early termination: [Provisions, penalties, notice period]

Compensation / Financial Terms:
- [Payment terms, amounts, schedule]
- [Price escalation or adjustment mechanisms]
- [Late payment penalties or interest]
- [Deposit, retainer, or upfront payment requirements]

Scope of Work / Services / Products:
- [Description of what is being provided or exchanged]
- [Acceptance criteria or performance standards]
- [Change order process if applicable]

─────────────────────────────────────────────

OBLIGATIONS AND RESPONSIBILITIES:

Client's Obligations:
1. [Obligation #1 — with section reference]
2. [Obligation #2 — with section reference]
3. [Obligation #3 — with section reference]

Counterparty's Obligations:
1. [Obligation #1 — with section reference]
2. [Obligation #2 — with section reference]
3. [Obligation #3 — with section reference]

─────────────────────────────────────────────

RISK ANALYSIS:

HIGH RISK — Requires Attention:
⚠ [Risk #1]: [Section reference] — [Explain the provision, why it is concerning,
   and the potential impact on the client. Suggest proposed revision language.]

⚠ [Risk #2]: [Section reference] — [Explanation and recommendation]

MODERATE RISK — Recommended Revision:
• [Risk #1]: [Section reference] — [Explanation and recommendation]
• [Risk #2]: [Section reference] — [Explanation and recommendation]

LOW RISK — Acceptable / Standard:
• [Item #1]: [Section reference] — [Note that this is standard / market]

─────────────────────────────────────────────

UNUSUAL OR NON-STANDARD PROVISIONS:
- [Provision #1]: [Section reference] — [Explain what is unusual about this
  provision compared to market standard and its potential impact]
- [Provision #2]: [Section reference] — [Explanation]

MISSING OR RECOMMENDED ADDITIONS:
- [Missing provision #1]: [Recommend adding — e.g., "No force majeure clause.
  Recommend adding standard force majeure provision."]
- [Missing provision #2]: [Recommendation]

─────────────────────────────────────────────

KEY PROTECTIVE PROVISIONS:

Indemnification:
- [Who indemnifies whom, scope, carve-outs, caps]
- [Assessment: adequate / needs revision]

Limitation of Liability:
- [Cap on liability — dollar amount or formula]
- [Exclusion of consequential, incidental, or punitive damages]
- [Carve-outs from the limitation]
- [Assessment: adequate / needs revision]

Insurance Requirements:
- [Required coverage types and amounts]
- [Additional insured requirements]

Intellectual Property:
- [Ownership of work product, pre-existing IP, licenses granted]
- [IP representations and warranties]

Confidentiality / Non-Disclosure:
- [Scope of confidential information]
- [Duration of obligation]
- [Permitted disclosures]

Non-Compete / Non-Solicitation:
- [Scope, duration, geographic limitation]
- [Enforceability assessment based on jurisdiction]

─────────────────────────────────────────────

DISPUTE RESOLUTION:
- Governing Law: [Jurisdiction]
- Venue: [Location]
- Mechanism: [Litigation / Arbitration / Mediation — mandatory or optional]
- Attorney's Fees: [Prevailing party provision — yes / no]

─────────────────────────────────────────────

RECOMMENDED REVISIONS SUMMARY:

| # | Section | Issue | Recommended Change | Priority |
|---|---------|-------|-------------------|----------|
| 1 | [Ref]   | [Issue] | [Proposed revision] | High |
| 2 | [Ref]   | [Issue] | [Proposed revision] | High |
| 3 | [Ref]   | [Issue] | [Proposed revision] | Medium |
| 4 | [Ref]   | [Issue] | [Proposed revision] | Low |

─────────────────────────────────────────────

OVERALL ASSESSMENT:
[Summary assessment of the contract from the client's perspective. Is this a
fair, balanced agreement? Does it disproportionately favor one party? Is it
ready for execution with minor revisions, or does it need substantial
renegotiation? Provide a clear recommendation.]

─────────────────────────────────────────────

Read the full file on GitHub · 179 lines

Changes

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.

  1. 12d ago First seen · 179 lines · 15 tokens per session scan A b057bc7624f2

Subscribe to this mod's changes

contract-summary is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,514 once invoked, about $0.0001 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.