Menu
Use when the agent is about to perform a risky operation (destructive shell, deploy, schema migration, money write, force-push). Reminds to record HITL approval and points at compliance/ templates.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | compliance |
| description | Use when the agent is about to perform a risky operation (destructive shell, deploy, schema migration, money write, force-push). Reminds to record HITL approval and points at compliance/ templates. |
Auto-activates when the agent is about to run a classified risky op:
rm_rf — destructive shell deletiondeploy — kubectl apply, docker compose up, terraform apply, etc.schema_migration — file in migrations/money_write — INSERT/UPDATE/DELETE against money tablesforce_push_main — git push --force to main / mastercompliance/HITL_TEMPLATE.md. If not, prompt the user to run /mek-init.compliance/DECISION_LOG.md with date, operator, op category, and short rationale.Quiet-by-default. The hook will WARN. To escalate to a hard block, set mek.toml > [compliance.gates] > <op> = "block".
Use after PR-sized work completes (or on /mek-drift) to compare auto scores against .mek/drift-baseline.json and surface divergences > 0.15.
STUB. Future v0.2.0 feature — a mini-SQLite ledger so the agent can record/query journal entries for any context (token spend, invoicing, etc.). Not active in v0.1.0.
Use when the agent encounters money-shaped identifiers (amount, price, balance, total, cost), performs arithmetic across monetary fields, or writes/reads money to a database. Enforces Decimal-only math.
Use when starting any conversation in a project where MEK is installed - announces the three guardrails (compliance, drift, ledger) and how to invoke them.