compliance-audit-workflow

compliance-audit-workflow is a skill for Claude Code from Swih/mistral-mcp. It costs 68 tokens per session (1,338 once invoked), scanned A, original, MIT.

A workflow for auditing a deployed Mistral Workflow against requirements such as GDPR, SOC 2, or PCI DSS. These are standards and laws for privacy, security controls, and payment-card data protection.

In plain words
What is it for?
Use it to audit a running compliance workflow, review live findings, respond to human-input checkpoints, and approve or escalate decisions.
Why use it?
It lets you inspect findings during the audit and make approval, escalation, or skip decisions at defined checkpoints.

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 audit a running compliance workflow, review live findings, respond to human-input checkpoints, and approve or escalate decisions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swih/mistral-mcp/compliance-audit-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 compliance-audit-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 compliance-audit-workflow

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/swih/mistral-mcp/compliance-audit-workflow"><img src="https://agentmods.dev/badge/skills/swih/mistral-mcp/compliance-audit-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,338 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.00068 $0.01338
Opus 5 $0.00034 $0.00669
Sonnet 5 $0.00014 $0.00268
Haiku 4.5 $0.00007 $0.00134

Measured 10d ago against content hash 7a6d07cc104a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

compliance-audit-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 10d 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/compliance-audit-workflow/SKILL.md · 169 lines

How it starts

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

Compliance audit workflow

Orchestrates a deployed Mistral Workflow for compliance auditing. Uses workflow_interact(action: "query") to inspect live findings mid-run, and workflow_interact(action: "signal") to approve, escalate, or skip at each decision checkpoint.

Profile note: workflow_execute, workflow_status, and workflow_interact are available in the core profile (default). files_upload (for uploading target documents) requires MISTRAL_MCP_PROFILE=full.

Temporal behavior: while the workflow is processing or waiting for a signal, its status remains RUNNING. Detect "waiting for human input" by querying a status handler, not by checking for a PAUSED status (which doesn't exist in this API).

Important: handler names are workflow-specific

Ask the user (or consult mistral://workflows) for:

  • The query handler that exposes current findings (e.g. "get_findings")
  • The query handler that exposes checkpoint state (e.g. "get_checkpoint")
  • The signal handler that receives audit decisions (e.g. "audit_decision")

Steps

Step 1 — Collect inputs

Ask the user for:

  1. workflowIdentifier — the deployed audit workflow name or ID
  2. scope — compliance framework: "GDPR", "SOC2", "PCI-DSS", "ISO27001", etc.
  3. Target documents: file_ids (upload via files_upload — requires full profile) or public URLs passed as workflow input
  4. Optional: audit_depth"quick" / "standard" / "full"
  5. Handler names (if non-default)

Step 2 — Launch the audit

Call workflow_execute:

{
  "workflowIdentifier": "<workflow name or ID>",
  "input": {
    "scope": "<GDPR|SOC2|PCI-DSS|ISO27001>",
    "document_ids": ["<file_id_1>", "<file_id_2>"],
    "audit_depth": "standard"
  }
}

Note structuredContent.execution_id. Confirm: "Audit workflow started — execution ID: <execution_id>."

Step 3 — Poll and query mid-run findings

Loop:

  1. Call workflow_status with { "executionId": "<execution_id>" }
  2. Check structuredContent.status:
    • COMPLETED → go to Step 5
    • FAILED / CANCELED / TIMED_OUT → surface error and stop
    • RUNNING → continue

Read the full file on GitHub · 169 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. 10d ago First seen · 169 lines · 68 tokens per session scan A 7a6d07cc104a

Subscribe to this mod's changes

compliance-audit-workflow is a skill published in the GitHub repository Swih/mistral-mcp (15 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,338 once invoked, about $0.0003 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.