Skip to content
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • RIVAL Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • RIVAL Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival
  1. Home
  2. Models
  3. Claude Opus 4.6
  4. Adversarial Contract Review

See how Claude Opus 4.6 compares on this challenge:

  • Claude Opus 4.6 vs Claude Sonnet 4.6
  • Claude Opus 4.6 vs Gemini 3.1 Pro Preview
  • Claude Opus 4.6 vs Z.ai: GLM 5

4 models have responded to the "Adversarial Contract Review" challenge. Compare their approaches side-by-side on RIVAL. This response is part of RIVAL's open dataset of 5,600+ AI model responses.

Rival
Models
CompareBest ForArena
Sign Up
Sign Up
Back to Claude Opus 4.6

Adversarial Contract Review

Claude Opus 4.6's response to the 'Adversarial Contract Review' challenge.

Claude Opus 4.6
February 4, 2026
Text

?
Prompt

Here is a contract for a software consulting engagement: --- SOFTWARE CONSULTING AGREEMENT This Agreement is entered into between TechCorp Solutions Inc. ("Client") and [Contractor Name] ("Contractor"). 1. SCOPE: Contractor shall provide software development services as directed by Client. Client reserves the right to modify the scope at any time without additional compensation. 2. PAYMENT: Contractor shall be paid $150/hour, invoiced monthly. Payment is due within 90 days of invoice receipt. Client may withhold payment if deliverables are deemed "unsatisfactory" at Client's sole discretion. 3. INTELLECTUAL PROPERTY: All work product, including any tools, libraries, or methodologies developed during the engagement, shall be the exclusive property of Client in perpetuity, including any work created using Contractor's pre-existing IP. 4. NON-COMPETE: Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination. 5. TERMINATION: Client may terminate this agreement at any time without notice. Contractor must provide 60 days written notice. Upon termination, Contractor must immediately deliver all work in progress without additional compensation. 6. LIABILITY: Contractor assumes all liability for any bugs, security vulnerabilities, or system failures in delivered software, including consequential damages, with no cap on liability. 7. INDEMNIFICATION: Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault. 8. CONFIDENTIALITY: Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination. 9. DISPUTE RESOLUTION: Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party. --- Find all clauses that could be exploited against the contractor, suggest specific modifications, and explain the legal reasoning.

Claude Opus 4.6
Response

claude-opus-4.6 logo
Claude Opus 4.6Adversarial Contract Review
claude-opus-4.6 logo
Claude Opus 4.6

Comprehensive Contract Analysis

This agreement is heavily one-sided and contains numerous provisions that could be exploited against the contractor. Below is a clause-by-clause analysis.


Clause 1: Scope — Unlimited Scope Creep Without Compensation

Problem: "Client reserves the right to modify the scope at any time without additional compensation."

This is essentially a blank check. The client could triple the workload, shift you to an entirely different project, or demand around-the-clock availability — all at the original rate with no recourse.

Suggested Revision:

Scope changes shall be documented in a written Change Order signed by both parties. Changes that materially alter the scope, timeline, or required skill set shall include revised compensation terms. If parties cannot agree on revised terms, either party may terminate under Section 5.

Legal Reasoning: Contracts require mutual consideration. A clause allowing one party to unilaterally redefine obligations undermines the definiteness required for contract formation. Courts sometimes void such provisions under the doctrine of illusory promises — if one party can change everything at will, the other party arguably received nothing definite in return.


Clause 2: Payment — Three Compounding Problems

Problem A: 90-Day Payment Terms

Net-90 is extreme for individual contractors. Combined with monthly invoicing, you could work for nearly four months before receiving any payment.

Problem B: Subjective Withholding Right

"Client may withhold payment if deliverables are deemed 'unsatisfactory' at Client's sole discretion" creates a mechanism for the client to simply never pay. There are no objective criteria, no cure period, and no obligation to articulate what is unsatisfactory.

Problem C: No Late Payment Penalties

There is no consequence for the client paying late or not at all.

Suggested Revision:

Payment is due within 30 days of invoice receipt. Invoices unpaid after 30 days shall accrue interest at 1.5% per month. If Client believes deliverables are unsatisfactory, Client must provide written notice specifying deficiencies within 10 business days of delivery. Contractor shall have 15 business days to cure. If Contractor cures the deficiencies, payment becomes immediately due. Client may not withhold more than 20% of any invoice amount during a dispute, and undisputed amounts must be paid on schedule.

Legal Reasoning: The "sole discretion" standard effectively gives the client a unilateral option not to perform its core obligation (paying). This may fail under the covenant of good faith and fair dealing implied in most jurisdictions. Courts have held that subjective satisfaction clauses must still be exercised honestly and in good faith, but proving bad faith is expensive — far better to define objective standards upfront.


Clause 3: Intellectual Property — Overreaching Ownership Claim

Problem: "including any tools, libraries, or methodologies developed during the engagement...including any work created using Contractor's pre-existing IP."

This clause attempts to seize your pre-existing intellectual property. If you use a personal framework you built over 10 years, the client could claim ownership of that framework. This could destroy your ability to work for any future client.

Suggested Revision:

Work Product created specifically for Client under this Agreement shall be assigned to Client upon full payment. Contractor's pre-existing IP ("Contractor Tools") remains the exclusive property of Contractor. Where Contractor Tools are incorporated into deliverables, Client receives a non-exclusive, perpetual, royalty-free license to use Contractor Tools solely as embedded in the delivered Work Product. Contractor shall identify pre-existing IP in writing before incorporating it.

Legal Reasoning: IP assignment clauses must be carefully scoped. Under Copyright Act §201(b), work-for-hire doctrine has specific statutory requirements and does not automatically apply to independent contractors. Many courts require explicit, specific assignment language, and overly broad assignments that capture pre-existing IP may be challenged as unconscionable. Additionally, if you use open-source components, this clause could put the client in violation of open-source licenses — creating liability for both parties.


Clause 4: Non-Compete — Likely Overbroad and Potentially Unenforceable

Problem: "not to provide similar services to any company in the same industry...for 24 months"

If the client is in, say, financial services, this clause bars you from doing any software consulting for any financial services company for two years. This could eliminate the majority of your livelihood.

Suggested Revision:

For a period of 6 months following termination, Contractor agrees not to provide services to the specific companies listed in Exhibit B that are direct competitors of Client. This restriction applies only to work substantially similar to the specific project scope defined in this Agreement. Client shall pay Contractor a monthly non-compete fee equal to 50% of Contractor's average monthly billings during the engagement for the duration of the restriction.

Legal Reasoning: Non-compete enforceability varies dramatically by jurisdiction. California (Business & Professions Code §16600) bans them almost entirely for independent contractors. Even in states that permit them, courts apply a reasonableness test evaluating duration, geographic scope, and scope of restricted activity. A 24-month industry-wide ban with no geographic limitation and no compensation would likely be deemed unreasonable in most jurisdictions. However, some states apply blue pencil doctrine — a court might narrow it rather than void it, leaving you uncertain about what is actually restricted.


Clause 5: Termination — Asymmetric and Punitive

Problem: Three layers of unfairness:

  • Client can terminate instantly without notice; contractor must give 60 days
  • Contractor must deliver all work in progress without additional compensation
  • No mention of payment for work already completed

This means the client could wait until a project is nearly complete, terminate, receive all work product, and arguably owe nothing for the final period.

Suggested Revision:

Either party may terminate with 14 days written notice. Upon termination, Client shall pay for all work performed through the termination date, plus a kill fee equal to 2 weeks of average billings. Work product shall be delivered only upon receipt of all outstanding payments. If Client terminates without cause, Contractor shall be paid for the full notice period regardless of whether services are requested.

Legal Reasoning: Courts examine termination clauses for unconscionability, particularly procedural unconscionability (unequal bargaining power) and substantive unconscionability (unreasonably one-sided terms). The requirement to surrender work without compensation may also constitute unjust enrichment. The asymmetric notice periods further evidence the one-sided nature of the agreement.


Clause 6: Liability — Unlimited and Unreasonable

Problem: "Contractor assumes all liability...including consequential damages, with no cap on liability."

You build a feature that processes payments. A bug causes a billing error. Under this clause, you are personally liable for every dollar of consequential damage — lost revenue, customer lawsuits, regulatory fines, reputational harm — with no ceiling. A single project could result in personal bankruptcy.

Suggested Revision:

Contractor's total aggregate liability under this Agreement shall not exceed the total fees actually paid to Contractor under this Agreement, or $[amount], whichever is less. Contractor shall not be liable for indirect, incidental, consequential, or punitive damages. Contractor warrants that services will be performed in a professional and workmanlike manner. Client acknowledges responsibility for independent testing, code review, and production deployment decisions.

Legal Reasoning: Unlimited liability with consequential damages is virtually unheard of in professional services contracts between sophisticated parties. Even large consulting firms like Accenture or Deloitte cap liability at the contract value. Courts may find unlimited liability provisions unconscionable, particularly when the contractor is an individual with no ability to absorb enterprise-scale losses. The clause also ignores contributory negligence — the client's own failure to test or review code.


Clause 7: Indemnification — "Regardless of Fault" Is the Poison Pill

Problem: "regardless of fault"

This means if the client's own employee introduces a security vulnerability into code you wrote, and a third party sues, you pay. This is not indemnification — it is blanket insurance at the contractor's expense.

Suggested Revision:

Each party shall indemnify the other against third-party claims arising from the indemnifying party's negligence, willful misconduct, or material breach of this Agreement. Contractor's indemnification obligation is subject to the liability cap in Section 6. Client shall promptly notify Contractor of any claim and allow Contractor to control the defense.

Legal Reasoning: Mutual indemnification is standard. One-way indemnification "regardless of fault" may be challenged as unconscionable and may conflict with public policy in jurisdictions that prohibit indemnification for one's own negligence (anti-indemnity statutes exist in many states, particularly in construction and services contexts).


Clause 8: Confidentiality — Gag Clause Masquerading as NDA

Problem: "Contractor shall not disclose any information about this engagement, including the terms of this agreement"

This prevents you from:

  • Listing the client on your resume or portfolio
  • Discussing payment disputes with an attorney (arguably)
  • Reporting illegal activity
  • Discussing wage information (which is federally protected under the NLRA)

Suggested Revision:

Contractor shall not disclose Client's proprietary business information or trade secrets for 2 years following termination. Contractor may disclose: (a) the existence of the engagement and general nature of services for portfolio purposes, (b) agreement terms to legal or financial advisors, (c) information required by law or regulation. Nothing in this clause restricts Contractor's rights under the National Labor Relations Act or applicable whistleblower protections.

Legal Reasoning: Overly broad confidentiality clauses can be struck down as restraints on trade. Under the NLRA, even independent contractors have certain rights to discuss compensation. The clause may also conflict with whistleblower protection statutes (Dodd-Frank, SOX, state equivalents) if it chills reporting of illegal activity.


Clause 9: Dispute Resolution — Structurally Disadvantageous

Problem: Binding arbitration in the client's home jurisdiction with loser-pays costs.

  • Loser-pays deters contractors from bringing legitimate claims because the financial risk of losing is catastrophic
  • Client's home jurisdiction forces you to travel and hire local counsel
  • Binding arbitration eliminates your right to a jury trial and severely limits appeals

Suggested Revision:

Disputes shall first be subject to good-faith mediation. If unresolved after 30 days, disputes shall be resolved by binding arbitration under AAA Commercial Rules. Arbitration shall take place in [neutral location or Contractor's jurisdiction], or by videoconference. Each party shall bear its own legal costs. Arbitration fees shall be shared equally, except that Client shall advance Contractor's share if the amount in controversy exceeds $50,000, subject to reallocation in the final award. Either party may seek injunctive relief in a court of competent jurisdiction.

Legal Reasoning: While arbitration clauses are generally enforceable under the Federal Arbitration Act, courts scrutinize clauses that effectively deny access to a forum. The combination of distant jurisdiction and loser-pays costs could be deemed procedurally unconscionable if it effectively prevents the contractor from vindicating their rights.


Critical Omissions — What the Contract Doesn't Say

The agreement is also dangerous for what it fails to include:

Missing ProvisionRisk
Independent Contractor StatusWithout explicit classification language, the IRS or state agencies could reclassify the relationship, creating tax liability for both parties
Insurance RequirementsNo mention of E&O insurance, leaving the contractor exposed under the unlimited liability clause
Force MajeureNo protection for events beyond contractor's control
Governing LawNo choice of law provision, creating uncertainty about which state's laws apply
Maximum Hours / AvailabilityCombined with the scope modification clause, the client could demand unlimited availability
Rate EscalationNo provision for rate increases on long engagements
Survival ClauseUnclear which provisions survive termination

Overall Assessment

This contract is not a negotiating starting point — it is a liability trap. The combination of unlimited scope changes, subjective payment withholding, pre-existing IP seizure, unlimited liability, and a gag clause creates a scenario where a contractor could:

  1. Have their workload doubled without compensation
  2. Have payment withheld indefinitely on subjective grounds
  3. Lose ownership of their pre-existing tools and frameworks
  4. Be personally liable for millions in consequential damages
  5. Be unable to work in the industry for two years
  6. Be unable to even discuss what happened

Recommendation: Do not sign this agreement as written. Provide a comprehensive redline incorporating the modifications above. If the client refuses to negotiate material changes — particularly to the liability cap, IP ownership, payment terms, and non-compete — that itself is a significant red flag about the engagement.

Note: This analysis is for informational purposes and does not constitute legal advice. Consult a licensed attorney in your jurisdiction before signing or negotiating any contract.

Adversarial Contract Review

Turn this model response into notes, narration, or a short video

Auto NotesTranscriptNarrateVideo Cut

Partner link

This output is part of our open dataset — 5K+ AI responses across 200 models

About Claude Opus 4.6

Capabilities

ConversationReasoningCode GenerationAnalysisTool Use

Categories

TextCodeMultimodal

Specifications

Provider
Anthropic
Released
2026-02-04
Size
XLARGE
Context
1,000,000 tokens

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Claude Opus 4.6 vs Gemini 3.1 Pro Preview

Both outputs, side by side

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • RIVAL Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival