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/fergupa/claude_plugins/review-contractgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/commands/fergupa/claude_plugins/review-contract)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/review-contract"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/review-contract.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 | $0.00021 | $0.01579 |
| Opus 5 | $0.00010 | $0.00790 |
| Sonnet 5 | $0.00004 | $0.00316 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
review-contract 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 4d 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.
This is a copy
100% identical to review-contract — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review-contract -- Contract Review Against Playbook
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Review a contract against your organization's negotiation playbook. Analyze each clause, flag deviations, generate redline suggestions, and provide business impact analysis.
Invocation
/review-contract
Workflow
Step 1: Accept the Contract
Accept the contract in any of these formats:
- File upload: PDF, DOCX, or other document format
- URL: Link to a contract in your CLM, cloud storage (e.g., Box, Egnyte, SharePoint), or other document system
- Pasted text: Contract text pasted directly into the conversation
If no contract is provided, prompt the user to supply one.
Step 2: Gather Context
Ask the user for context before beginning the review:
- Which side are you on? (vendor/supplier, customer/buyer, licensor, licensee, partner -- or other)
- Deadline: When does this need to be finalized? (Affects prioritization of issues)
- Focus areas: Any specific concerns? (e.g., "data protection is critical", "we need flexibility on term", "IP ownership is the key issue")
- Deal context: Any relevant business context? (e.g., deal size, strategic importance, existing relationship)
If the user provides partial context, proceed with what you have and note assumptions.
Step 3: Load the Playbook
Look for the organization's contract review playbook in local settings (e.g., legal.local.md or similar configuration files).
The playbook should define:
- Standard positions: The organization's preferred terms for each major clause type
- Acceptable ranges: Terms that can be agreed to without escalation
- Escalation triggers: Terms that require senior counsel review or outside counsel involvement
If no playbook is configured:
- Inform the user that no playbook was found
- Offer two options:
- Help the user set up their playbook (walk through defining positions for key clauses)
- Proceed with a generic review using widely-accepted commercial standards as the baseline
- If proceeding generically, clearly note that the review is based on general commercial standards, not the organization's specific positions
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.
- 4d ago First seen · 170 lines · 21 tokens per session scan A 5e6ab577c63a
review-contract is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,579 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-contract, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.