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 skills add travisjneuman/.claude --skill contract-redlinergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/skills/travisjneuman/.claude/contract-redliner)<a href="https://agentmods.dev/skills/travisjneuman/.claude/contract-redliner"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/contract-redliner/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.
<a href="https://agentmods.dev/skills/travisjneuman/.claude/contract-redliner"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/contract-redliner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.03587 |
| Opus 5.5 | $0.00016 | $0.01435 |
| Sonnet 5.5 | $0.00008 | $0.00717 |
| Haiku 4.5 | $0.00004 | $0.00359 |
Grade A, and why
contract-redliner 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 28d 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 — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Redliner
Systematic contract review methodology with clause-by-clause analysis, risk scoring, redline markup, and negotiation strategy for commercial agreements.
Contract Review Methodology
Systematic Review Process
PHASE 1: TRIAGE (5 minutes)
- Identify contract type (SaaS, services, licensing, employment, NDA)
- Determine your party's position (buyer/seller, licensor/licensee)
- Note contract value and term
- Flag overall risk level for appropriate review depth
PHASE 2: STRUCTURAL SCAN (10 minutes)
- Verify all standard sections present
- Check for missing critical clauses
- Note any unusual structure or ordering
- Identify exhibits, schedules, and SOWs
PHASE 3: CLAUSE-BY-CLAUSE REVIEW (bulk of time)
- Review each clause against standard/market terms
- Score risk level per clause
- Draft redline markup for non-standard terms
- Note clauses requiring business input
PHASE 4: RISK SUMMARY AND REDLINE (10 minutes)
- Compile risk register
- Prioritize redlines (must-have vs nice-to-have)
- Draft negotiation talking points
- Prepare executive summary
Review Depth by Contract Value
| Contract Value | Review Depth | Reviewer Level | Turnaround |
|---|---|---|---|
| < $25K | Light scan, template comparison | Paralegal / Junior | 1-2 days |
| $25K - $250K | Standard clause review | Associate | 3-5 days |
| $250K - $1M | Deep review with risk memo | Senior Associate | 5-7 days |
| $1M - $10M | Full review + negotiation strategy | Senior Attorney | 7-14 days |
| > $10M | Multi-lawyer review + specialist input | Partner-led team | 14-30 days |
Common Clause Types
Standard vs Non-Standard Terms
| Clause | Standard/Market | Watch For |
|---|---|---|
| Term | 1-3 years with auto-renewal | Evergreen with difficult termination |
| Termination for Convenience | 30-90 days notice | No convenience termination right |
| Limitation of Liability | Cap at 12 months fees paid | Uncapped liability, one-sided |
| Indemnification | Mutual, limited to IP and breach | Unlimited, one-sided, broad triggers |
| Confidentiality | 2-5 year survival, mutual | Perpetual, asymmetric obligations |
| IP Ownership | Each party retains pre-existing IP | Broad assignment of derivative works |
| Warranty | Industry-standard warranties | Excessive warranties or broad disclaimers |
| Data Protection | DPA aligned with applicable law | No DPA, weak data obligations |
| Force Majeure | Mutual, covers standard events | One-sided, too broad or too narrow |
| Governing Law | Counterparty's or neutral jurisdiction | Inconvenient or unfavorable forum |
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.
- 28d ago Changed a1ef1b20f2d7
- 1mo ago First seen · 451 lines · 41 tokens per session scan A 9a88fa044bcd
contract-redliner is a skill published in the GitHub repository travisjneuman/.claude (106 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 3,587 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…