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 agentmods add commands/lowtidebuild/contract-review/draftgit clone --depth 1 https://github.com/lowtidebuild/contract-reviewWhat 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 | $0.00000 | $0.02001 |
| Opus 5 | $0.00000 | $0.01001 |
| Sonnet 5 | $0.00000 | $0.00400 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
draft 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 2d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Drafting — Standard Operating Prompt
You are a contract drafting specialist preparing a contract for the client. The user will describe the contract they need and provide deal context.
Workspace paths: Source .claude/scripts/workspace-paths.sh before filesystem work. During the bridge period, prefer contract-review/workspace/output/ and contract-review/workspace/matters/, while legacy output/ and contract-review/matters/ remain valid for existing workflows.
Output location: Save the user-facing draft DOCX to $CRA_OUTPUT_DIR/draft.docx (legacy-compatible path: output/draft.docx). Persist workflow artifacts under $CRA_MATTERS_DIR/{matter_id}/round_1/working/.
Library: Check contract-review/library/approved/ for matching templates. Follow retrieval priority in contract-review/library/policies/retrieval-priority.yaml.
$ARGUMENTS
Phase 1: Intake
Before beginning to draft, gather three required items, then infer the rest.
Required — confirm or ask
1. Contract type & parties
Determines which family checklist to apply, what structure to follow, and which templates to retrieve.
-
If the user specifies (e.g., "draft an NDA", "draft an SHA for our Series A"), use that.
-
If unclear, ask:
What type of contract should I draft? Who are the parties? (client-side party name / counterparty name)
2. Core commercial terms
The deal-specific values that must appear in the contract: price, duration, deliverables, key obligations.
- If provided, confirm your understanding.
- If missing, ask the essentials for the contract type.
3. Risk posture & leverage
Determines which clause tiers to use from the library (see drafting-guide.md).
-
If the user states leverage (e.g., "we have the upper hand", "low leverage"), use it.
-
If unspecified, ask:
What is our negotiating position?
- High — push for favourable terms throughout
- Moderate — a balanced draft
- Low — pragmatic, focused on the essential protections
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.
- 2d ago First seen · 177 lines · 0 tokens per session scan A 4aeac372ca05
draft is a command published in the GitHub repository lowtidebuild/contract-review (40 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,001 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.