contract-review-workflow

contract-review-workflow is a skill for Claude Code from Swih/mistral-mcp. It costs 37 tokens per session (769 once invoked), scanned A, original, MIT.

A workflow integration that sends contracts to a deployed Mistral Workflow for multi-step review and waits for human decisions when required.

In plain words
What is it for?
Use it to upload and review contracts, check workflow status, inspect approval checkpoints, collect a person’s approval or requested changes, and resume the review.
Why use it?
It supports reviews that may include document text extraction, clause analysis, legal-data lookup, and risk scoring while preserving progress across retries or restarts.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mistral-mcp plugin — 11 skills shipped together

Good fit Use it to upload and review contracts, check workflow status, inspect approval checkpoints, collect a person’s approval or requested changes, and resume the review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swih/mistral-mcp/contract-review-workflow
Install

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.

Any agent
npx skills add Swih/mistral-mcp --skill contract-review-workflow
Clone the repo
git clone --depth 1 https://github.com/Swih/mistral-mcp

Made for: Claude Code.

Or install mistral-mcp, the plugin that ships this one along with the rest of its 11 skills.

Wrote 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.

agentmods badge for contract-review-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/swih/mistral-mcp/contract-review-workflow/github.svg)](https://agentmods.dev/skills/swih/mistral-mcp/contract-review-workflow)
Your own site
<a href="https://agentmods.dev/skills/swih/mistral-mcp/contract-review-workflow"><img src="https://agentmods.dev/badge/skills/swih/mistral-mcp/contract-review-workflow/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.

agentmods 80×15 button for contract-review-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/swih/mistral-mcp/contract-review-workflow"><img src="https://agentmods.dev/badge/skills/swih/mistral-mcp/contract-review-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00769
Opus 5.5 $0.00015 $0.00308
Sonnet 5.5 $0.00007 $0.00154
Haiku 4.5 $0.00004 $0.00077

Measured 27d ago against content hash 035aa4fef389, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

contract-review-workflow 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 27d 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.

claude-plugin/skills/contract-review-workflow/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Contract review workflow

Requires workflow_execute, workflow_status, and related workflow tools in workflows, metier-docs, or admin. They are absent from core. Check mistral://capabilities first. This skill does not create a workflow or supply a contract approval system.

Establish the deployment contract

Read mistral://workflows to identify the requested definition, and call workflow_deployments_list with {} to check deployments and live workers. A catalog entry alone does not prove that the workflow is runnable. If runnable_count is zero, report that a deployment must be started. Confirm which active deployment serves the selected workflow before execution.

Obtain its documented input schema, output meaning, checkpoint query names, decision handlers, and payload shapes from the workflow documentation or owner. The discovery resource lists metadata, not these contracts. Do not invent document fields, review modes, approval handlers, or a standard checkpoint object.

Use only document representations that this deployment accepts. A local document can be converted to text with an available converter; files_upload requires admin and takes file bytes in content_base64, with filename and purpose: "ocr" for a PDF. Its ID is structuredContent.id. A file ID is useful only if the workflow accepts it.

If no suitable deployment exists, explain the requirement. For direct extraction, use the contract-analyzer skill when process_document is exposed; extraction does not provide an approval workflow.

Execute and follow the run

Call workflow_execute with:

  • workflowIdentifier: the verified workflow name or ID.
  • input: a JSON object matching that workflow's input contract; omit only if no input is required.
  • deploymentName: the verified target deployment when needed.
  • waitForResult: false for workflows with human checkpoints.

Check isError and save structuredContent.execution_id. Poll workflow_status with { "executionId": "<returned execution ID>" }. Use spaced, bounded checks and retain the ID so the user can resume tracking.

Read the full file on GitHub · 40 lines

Changes

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.

  1. 27d ago Changed · -85 lines · -24 tokens per session 035aa4fef389
  2. 1mo ago First seen · 125 lines · 61 tokens per session scan A 75dfcfa11920

Subscribe to this mod's changes

contract-review-workflow is a skill published in the GitHub repository Swih/mistral-mcp (15 stars, last pushed 26d ago), licensed MIT. It adds 37 tokens to every session and 769 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories