Skip to main content

Agent pack

Contract clause finder

What does clause X say across all our agreements, answered with page references.

By
Caleb and Ryan, the founders
Updated
September 2, 2026
Version
0.1, in the library
  • Claude Code
  • Anthropic API

An agent over a folder of contracts: ask what the termination terms are across your vendor agreements and get the answer with the document and page each claim comes from. It cites or it says it cannot find it; it never paraphrases from memory. The pattern behind our contract-intelligence client work, in its general form.

Built, documented, running.

Part of the working library we deploy from on every engagement.

Bring this into a project

Runs on

  • Claude Code
  • Anthropic API

2 requirements, below.

  • Complete and documented: the same files we run ourselves.
  • Deployed and tuned to your stack as part of an engagement.

The file

Draft excerpt
# Citation rules 1. Every claim names its document and page.2. Not found is a valid answer; a guess is not.3. Conflicting clauses are surfaced, not resolved silently.4. The human reads the page before acting. Always.

What is inside

3 items. Includes deployment guide.

  • AGENT.mdThe finder: cite or decline, never guess
  • citation-rules.mdWhat counts as an answer
  • guide.mdOrganizing the folder so answers stay sharp

Who it is for

  • Contract questions mean finding the document, then finding the page.
  • Renewals surprise you because the terms live in twelve PDFs.
  • One careful person is the only one who knows what was signed.

Requirements

  • Contracts as PDFs in one folder
  • An agent runtime with file access

Where this sits

  1. This system

    Contract clause finder

    In the library, running.

  2. In your stack

    Deployed on an engagement

    The audit finds which system earns its place first; we install and tune it around how you work.

Changelog

  1. September 2, 2026In the library. Version 0.1 runs in our own operation.

Related

  1. Agent pack

    Document intake and extraction

    Paperwork reads itself and files its own fields

    Works with n8n, Anthropic API.

    Built and running

  2. Workflow

    Meeting actions router

    Every commitment made in a meeting lands where work happens, owned and dated

    Works with n8n, Anthropic API.

    Built and running

  3. Workflow

    Document restructure pipeline

    A dense document reshaped into your required structure, with a human approving every output

    Works with Claude Code, Anthropic API.

    Built and running