Automode Policy

Auto-mode policy (automode-policy)

Trigger phrases: "auto mode", "classifier policy", "permission classifier", "autoMode settings", "policy pack"

Purpose: the kit's gates run at the tool level (guard-bash.sh, the git hooks) and that is where its enforcement stays. Since 2026-08-14 auto mode is the default permission mode on Pro/Max/Team, putting a classifier in front of the same actions. This skill lets you see and audit that classifier's configuration. It does not add a gate — read the measurement below before treating it as one.

Measured: these rules did not enforce

Claude Code 2.1.238, 2026-08-24, interactive session, permissionMode=auto, this policy installed in user settings, claude auto-mode config listing all three rules:

The kit's rule names git reset --hard and git clean -fd verbatim and declares them unconditional, so the wording is not the variable. The control run shows the classifier did not gate this class of action at all, with or without custom rules. Whatever autoMode prose rules do, they are not a substitute for a gate.

What did protect the work in every run was the model choosing to back it up first — discipline, not a gate. The kit exists because discipline is the thing that fails silently.

Why this is the kit's only out-of-project file

The classifier reads autoMode from user settings (~/.claude/settings.json) or managed settings. It deliberately ignores .claude/settings.json and .claude/settings.local.json, because a checked-in repo could otherwise ship its own allow rules. So a plugin cannot install this policy — an installer must, with the user's word. That is scripts/apply.sh, and it asks before it writes.

The failure this still catches — the reason to keep the skill

Setting an autoMode array without the literal "$defaults" replaces the built-in list for that section. Measured on Claude Code 2.1.238: dropping "$defaults" took soft_deny from 66 rules to 2 — force push, piping a downloaded script into a shell, production deploys and auto-mode bypass all gone — with no error and no warning. The session looks healthy. scripts/check.sh reads what the classifier actually uses (claude auto-mode config), not the policy file, because a policy file that parses is not a policy that applies.

What the kit puts in the config (present, not proven to enforce)

Deliberately not set: environment (your trusted repos/buckets/domains — guessing them either over-trusts or, set without "$defaults", wipes the built-in list) and allow (loosening is the user's call, never the kit's). §4.4 needs nothing here: content-scoped permissions.ask rules already force a prompt in auto mode, and the kit ships those in project settings.

How

bash .claude/skills/automode-policy/scripts/check.sh          # inspect the effective config
bash .claude/skills/automode-policy/scripts/apply.sh          # propose → diff → ask → install → verify
bash .claude/skills/automode-policy/scripts/apply.sh --strict # also route EVERY shell command to the classifier
bash .claude/skills/automode-policy/scripts/apply.sh --print  # print the block, paste it yourself

Verifying is read-only for the kit but not for Claude Code: claude auto-mode config rewrites its own settings.json as it reads (reformatted, model aliases normalised, a backups/ directory created). Measured, not assumed — it matters if you diff that file in CI.

check.sh exit codes: 0 config as expected · 2 built-ins dropped · 3 kit rules absent/partial · 4 cannot read the config (CLI too old, or auto mode unavailable on this account). /doctor-csk reports the same check.

--strict sets autoMode.classifyAllShell, which suspends narrow Bash/PowerShell allow rules while auto mode is active so every shell command reaches the classifier. It buys coverage with latency and one classifier call per command — offer it, don't assume it.

Rules

• Never install this silently. It writes outside the project; apply.sh asks, backs up, and restores the backup itself if the post-install check fails.
• Never hand-merge the user's settings file. Without jq or python3, apply.sh prints the fragment and stops — a half-written global settings file is worse than an uninstalled policy.
• Keep "$defaults" verbatim in every array you touch, including any rule you add later.
• Do not present this as a gate. The kit's enforcement is permissions.deny and the PreToolUse hooks, both of which are measured firing in smoke-test. This skill reports configuration.
• Re-measure before that changes. The table above is one version on one day; if a release makes custom autoMode rules enforce, this skill's claim can grow — but only with a run that shows a block.