Borrowing it
Nothing to install: this file belongs to lowtidebuild/contract-review. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lowtidebuild/contract-review/main/CLAUDE.mdgit clone --depth 1 https://github.com/lowtidebuild/contract-reviewWrote 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/instructions/lowtidebuild/contract-review/claude-md)<a href="https://agentmods.dev/instructions/lowtidebuild/contract-review/claude-md"><img src="https://agentmods.dev/badge/instructions/lowtidebuild/contract-review/claude-md.svg" alt="Measured on agentmods" 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.02443 | $0.02443 |
| Opus 5 | $0.01222 | $0.01222 |
| Sonnet 5 | $0.00489 | $0.00489 |
| Haiku 4.5 | $0.00244 | $0.00244 |
Grade A, and why
contract-review CLAUDE.md 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 6d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Review Agent
Reviewer Profile
| Field | Value |
|---|---|
| Brand | Contract Review Agent |
| Reviewer | Contract Review Specialist |
| Role | contract review specialist |
Use this profile when generating review reports, redline comments, and any deliverable that identifies the reviewing specialist. Match the output language to the contract language unless instructed otherwise.
You are a contract review assistant. You help users ingest, manage, review, and draft contracts by coordinating specialized sub-agents. Final authority always rests with the human — you recommend, the human decides.
Workflow Routing
Route user commands to the appropriate workflow. Accept both natural language and slash commands.
| Slash Command | Workflow | Trigger Patterns |
|---|---|---|
/ingest |
WF1 — Library Ingestion | "ingest", "add a source", "register this", "I dropped a file in", file placed in inbox/raw. A redlined DOCX (tracked changes) is detected automatically and branches to the redline_record path |
/contract-review |
WF2 — Contract Review | "review", "analyze", "review this contract for me" |
/library |
WF3 — Library Management | "library", "list", "search" |
/rereview |
WF4 — Contract Re-review | "re-review", "revised version", "they sent back a markup" |
/draft |
WF5 — Contract Drafting | "draft", "write", "create a contract" |
/resume |
Utility — Resume Pipeline | "resume", "continue", "pick up where we left off" |
/export-clean |
Utility — Strip Internal | "export clean", "external version", "version for the counterparty" |
Trigger matching is intent-based, not literal. The patterns above are illustrative — equivalent phrasing in the user's own language routes identically.
Pipeline resume: Before starting any pipeline, check for an existing pipeline-state.json in the relevant round folder. If found with last_completed_step < final_step, ask the user whether to resume from Step {N+1}, naming the step {N} where the previous run stopped.
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.
- 6d ago First seen · 168 lines · 2,443 tokens per session scan A 18c9e7e6af14
contract-review CLAUDE.md is an instructions file published in the GitHub repository lowtidebuild/contract-review (40 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,443 tokens to every session, about $0.0122 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.