ai-agents-config-cataloglisted

Catalog of every configuration axis in this repo, env vars, commit markers, frontmatter keys, QA skip verdicts, and escape hatches, each with its enforcement point and abuse story, plus the checklist for adding a new flag safely. Use when you say `what does a skip flag do`, `list escape hatches`, `can I skip this gate`, `add a config flag`. Do NOT use for hook runtime behavior (use `agent-harness-reference`) or change gating policy (use `ai-agents-change-control`).
rjmurillo/ai-agents · ★ 42 · AI & Automation · score 77

Install: claude install-skill rjmurillo/ai-agents

# AI Agents Config Catalog  Every flag, marker, and skip semantic in this repo, verified against code as of 2026-07-03. Hook registration surfaces were rechecked on 2026-08-14. Each escape hatch exists because a gate sometimes misfires; each one also has an abuse story or a guard. Before you set any of these, read its row. The house rule (learned in session 1187, see the Removed Flags section): escape hatches get teeth or get abused. Related skills: `ai-agents-change-control` owns when a bypass is allowed; `agent-harness-reference` and `ai-agents-architecture-contract` own what the hooks themselves do; `ai-agents-debugging-playbook` owns triaging a gate that fired on you. ## Triggers - `what does the skip-drift-check marker do` - `list escape hatches` - `can I skip this gate` - `add a config flag` - `is this skip marker allowed` ## Process 1. Identify the axis type: env var, commit marker, text directive, frontmatter key, file, or verdict string. 2. Find its row in the tables below. Read the effect AND the guard/abuse column before using it. 3. If you are about to use an escape hatch, confirm the legitimate trigger condition holds (for example, a workflow actually unrunnable under act). Bypassing because a gate is